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, settling the data from the previous calendar day at 00:00 each day. Bills are synchronized to the Billing Center.

Settlement Process¶

1. Separately count the data volume generated by each service within the workspace.
2. Generate bill details based on the counted traffic.
3. Synchronize bill data to the Billing Center for deduction according to the selected settlement method.
   • Billing Center direct settlement (top-up, prepaid card)
   • Cloud vendor direct debit settlement (Huawei Cloud, Alibaba Cloud, Amazon Web Services, Microsoft Azure)

Concepts¶

Billing Items¶

Time Series¶

Counts the number of unique tag combinations per metric reported via DataKit on the current day (per thousand per day).

For more details, refer to Time Series Logic Explained.

Metric Points¶

Fully counts all metric data points reported within the storage period (per ten million points).

Logs¶

Corresponding billing methods are provided based on feature usage and storage method.

Standard Storage¶

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

Billing by Number of Data Entries¶

Counts the number of newly reported data entries per day, including data generated by features like logs and events (per 1 million entries per day).

Billing by Ingested Log Volume¶

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

Long-term Storage¶

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

Index Advanced Matching¶

Counts the average daily data volume processed by Index Advanced Matching (GB/day).

Traces¶

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

• If Number of Traces ≥ Number of Spans / 10, billing is based on the number of Traces.
• Otherwise, billing is based on the number of Spans.

Application Performance Profile¶

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

RUM PV¶

Counts the number of reported page views from user visits (per ten thousand PVs per day).

Session Replay¶

Counts the number of session_ids with has_replay: true (per thousand Sessions per day).

Network¶

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

Synthetic Tests¶

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

Test Execution Count:

Enabled Synthetic Test tasks return results via the test nodes provided by Guance. Counts the number of new test data entries added within each hour interval (per ten thousand API tests per day).

Each browser test execution counts as 10 times, while other test types count as 1 time per execution. When using self-built test nodes, the billing count is calculated as 1/10 of the public test nodes, i.e., each browser test execution counts as 1 time, and other test types count as 0.1 times per execution.

Test Data Storage:

Counts the number of newly reported synthetic test data entries per day (per million entries per day).

Triggers¶

Counts the total daily sum of executions based on scheduled tasks from monitors, intelligent monitoring, SLOs, metric generation, etc., plus executions of officially provided advanced functions and query calls via DataKit or OpenAPI (per ten thousand times per day).

Calculation Examples¶

1. Standard Case: Execute 1 "Sudden Change Detection" → 5 Trigger calls.
2. Exceeding Detection Interval: Execute 1 "Outlier Detection" with a 30-minute detection interval → Base 5 times + exceeding portion (30-15=15 minutes, 15/15=1) → Total 6 times.
3. Multiple Detections with Exceeding Interval: Execute 2 "Range Detections" with a 60-minute detection interval → Base 2×5=10 times + exceeding portion (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 Scanned Volume¶

Counts the original volume 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 desensitization rule processing, the system will bill separately for the desensitization scanning of these three fields.

Security Detection Scanned Volume¶

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

Error Issue Records¶

Counts the number of newly associated error data entries per day, including error data reported to the Error Center (per 1,000 entries per day).

Scheduled Reports¶

The number of times scheduled reports are sent daily within the workspace (per time per day).

Central Pipeline¶

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

SMS¶

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

Phone Call (IVR)¶

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

Obsy AI¶

Obsy AI Service Subscription¶

Counts the subscription fee for the Obsy AI service package level within the workspace.

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

Package Upgrade

Users upgrading the Obsy AI service package do not require manual approval. When the workspace balance is sufficient, the system will immediately deduct the fee and generate a bill, with package benefits and complimentary credits taking effect simultaneously.

Complimentary Credits

By Credits¶

Counts the total daily Credits consumption generated by Obsy Agent Team and Obsy AI Assistant (per 10 Credits / day).

Billing Method: Obsy AI Credits adopt a prepaid top-up model, not supporting pay-as-you-go or postpaid settlement. Users need to contact their account manager to pre-purchase and top up Credits at the unit price corresponding to the current site and currency.

Deduction Rule: The system prioritizes using package complimentary credits for deduction. After package credits are exhausted or expired, it continues to deduct pre-purchased credits. Pre-purchased credits do not expire. When the credit balance is depleted, services related to Obsy AI Q&A and Agent invocation will be unavailable and require top-up to continue.

Credits Unit Price

Further Reading¶

You might also want to know: