Commercial Plan Billing Logic¶

Guance Commercial Plan adopts a pay-as-you-go model, with the workspace as the billing unit. The billing cycle is calculated daily, with settlement at midnight for the previous day's data. Invoices are synchronized to the Billing Center.

Settlement Process¶

1. Independently calculate the data volume generated by each service within the workspace.
2. Generate invoice details based on the calculated traffic.

3. Synchronize invoice data to the Billing Center, and deduct according to the selected settlement method.

   • Direct settlement at the Billing Center (recharge, prepaid cards)
   • Cloud vendor agency deduction settlement (Huawei Cloud, Alibaba Cloud, AWS, Microsoft Azure)

Concepts¶

Billing Items¶

Time Series¶

Counts the number of tag combinations corresponding to each metric in the metric data reported by DataKit on the current day (per thousand series/day).

For more details, refer to Time Series Logic Explanation.

Metric Points¶

Counts all metric data points reported during the storage period (per ten million data points).

Logs¶

Based on feature usage and storage methods, corresponding billing methods are provided.

Standard Storage¶

By default, billing is based on "Number of Log Data Entries". If you need to adopt the billing model based on "Ingested Traffic", please contact your account manager.

Billing by Data Entries¶

Counts the number of new data entries reported daily, including data generated by logs, events, and other features (per 1 million entries/day).

Billing by Ingested Traffic¶

Counts the size of the original log write traffic reported by users (before compression, per GB/day).

Long-term Storage¶

The log long-term storage billing amount is calculated based on the original storage volume of log data within the current total long-term storage period, minus the original storage volume of logs within the standard storage period (per GB/day). That is, only log data exceeding the standard storage duration is billed.

Index Progressive Matching¶

Counts the average daily data volume processed by index progressive matching (GB/day).

Traces¶

The system intelligently selects the billing method based on actual statistics:

• If Trace Count >= Span Count / 10, billing is based on Trace count.
• Otherwise, billing is based on Span count.

Application Performance Profile¶

Counts the number of Application Performance Profile data reported (per ten thousand entries/day).

RUM PV¶

Counts the number of page views reported by user access (per ten thousand PV/day).

Session Replay¶

Counts the number of session_id values with has_replay: true (per thousand Sessions/day).

Network¶

Counts the number of host values in the network data reported by eBPF within the workspace (per host reporting network data/day).

Synthetic Tests¶

Synthetic Tests have two billing items: "Test Execution Counts" and "Test Data Storage".

Test Execution Counts:

When a synthetic test task is enabled and returns test results through Guance's testing nodes, the number of new test data entries is counted at hourly intervals (per 10,000 API Tests/day).

Each execution of a browser test counts as 10, and each execution of other test types counts as 1. When using self-built testing nodes, the billing count is 1/10 of that for public nodes. That is, each execution of a browser test counts as 1 billing, and each execution of other test types counts as 0.1 billing.

Test Data Storage:

Counts the number of new test data entries reported daily (per million entries/day).

Triggers¶

Counts the total number of daily executions of scheduled tasks based on monitors, intelligent monitoring, SLOs, metric generation, official advanced function execution calls, and DataKit or OpenAPI query calls (per 10,000 times/day).

Calculation Example¶

1. Standard Case: 1 execution of "Mutation Detection" -> 5 task calls.

2. Exceeding Detection Interval: 1 execution of "Outlier Detection", detection interval 30 minutes -> Base 5 times + Exceeding part (30-15=15 minutes, 15/15=1) -> Total 6 times.

3. Multiple Detections with Exceeding Intervals: 2 executions of "Interval Detection", detection interval 60 minutes -> Base 2x5=10 times + Exceeding part (60-15=45 minutes, 45/15=3) -> Total 13 times.

Data Forwarding¶

Based on the data forwarding archive type, there are two billing categories.

Sensitive Data Scanning Traffic¶

Counts the original traffic size of sensitive data scanned based on scanning rules (per GB/day).

If a log data entry A needs to be scanned, and three fields within this data require masking rules, the system will bill for the masking scan of these three fields separately.

Security Detection Scanning Traffic¶

Counts the actual data size scanned by security detection rules daily (compressed) (per GB/day).

Error Entry Count¶

Counts the number of new error entries associated daily, including error data reported to the error center (per 1,000 entries/day).

Scheduled Report¶

Counts the number of times a scheduled report is sent daily within the workspace (per time/day).

Central Pipeline¶

Counts the data size of all original logs processed by the central Pipeline (per GB/day).

SMS¶

Counts the number of SMS messages sent on the current day (per 10 messages/day).

Voice Call¶

Counts the number of voice notifications sent daily (per time/day).

Obsy AI¶

Obsy AI Service Subscription¶

Counts the plan level and subscription fee of the Obsy AI service within the workspace.

Billing Cycle: The subscription cycle is based on the activation date, with automatic renewal on the same day each month. If the date does not exist in a month, renewal occurs on the last day of that month, without changing the original cycle base date for subsequent months. For example: Activated on January 31, renewed on February 28/29, and still renewed on March 31.

Plan Upgrade

When users upgrade their Obsy AI service plan, no manual approval is required. If the workspace balance is sufficient, the system will immediately deduct the fee and generate an invoice. The plan benefits and plan bonus credits take effect simultaneously.

Bonus Credits

By Credits¶

Counts the total Credits consumed by Obsy Agent Teams and Obsy Copilot on the current day (per 10 Credits/day).

Billing Method: Obsy AI Credits use a prepaid top-up model, which does not support pay-as-you-go or postpaid settlement. Users need to contact their account manager to prepurchase and top up Credits based on the current site and currency unit price.

Deduction Rule: The system first uses plan bonus credits for deduction. After plan credits are used up or expire, prepaid credits are deducted. Prepaid credits do not expire. When the credit balance is exhausted, Obsy AI Q&A and Agent-related services will no longer be available. Top-up is required to continue using the services.

Credit Unit Price

Further Reading¶

You may also want to learn about: