Commercial Plan Billing Logic¶

The Guance Commercial Plan uses a pay-as-you-go model, with the Workspace as the billing unit. The billing cycle is calculated by day. At 00:00 every day, the previous calendar day's data is settled, and bills are synced to the Billing Center.

Settlement Process¶

1. Individually count the data volume generated by each service in the Workspace;
2. Generate billing details based on the counted traffic;

3. Sync the billing data to the Billing Center and deduct the fee according to the selected settlement method.

   • Direct settlement in the Billing Center (top-up, Prepaid Card)
   • Deduction and settlement via cloud providers (Huawei Cloud, Alibaba Cloud, AWS, Microsoft Azure, etc.)

Concepts¶

Billing Items¶

Metrics Billing Methods¶

Metrics are billed by data points by default, and billing by time series is also supported.

Data Points¶

Counts all metric data points reported within the storage period (per 10 million data points).

Time Series¶

Counts the number of tag combinations for each metric in the metric data reported by users via DataKit on the current day (per 1,000/day).

For more details, see Detailed Explanation of Time Series Logic.

Logs¶

Billing methods are provided according to feature usage and storage method.

Standard Storage¶

Billing is metered based on data entries by default. If you need to use the billing by ingested volume model, contact your Account Manager.

Billing by Data Entries¶

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

Billing by Ingested Volume¶

Counts the log write volume reported by users and bills based on the data volume before compression (per GB/day).

Long-term Storage¶

Long-term log storage is billed based on the log data volume that exceeds the standard storage duration (per GB/day). The billing scope covers all log data in the total long-term storage period that exceeds the standard storage period. Data within the standard storage period is not billed again.

Index Advanced Matching¶

After you enable "Advanced Matching" for a log index, the system matches and processes log data through the Central Pipeline based on the configured conditions.

In addition to the fees generated by the logs themselves, Advanced Matching is also billed based on the data volume actually processed by the Central Pipeline (per GB/day). See Central Pipeline for the specific billing rules.

Trace¶

The trace billing scope includes Application Performance Monitoring (APM) and Agent monitoring data. Traces from Agent monitoring are counted with deduplication by trace_id, and spans are counted by new entries per day. The system intelligently selects the billing method based on actual statistics:

• If the Trace count ≥ Span count/10, billing is by Trace count;
• Otherwise, billing is by Span count.

APM Profile¶

Counts the number of APM Profile data records reported (per 10,000 records/day).

RUM PV¶

Counts the number of page views reported by RUM (per 10,000 PV/day).

Session Replay¶

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

Network¶

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

Synthetic Testing¶

Synthetic Testing has two billing items: "Synthetic Test Execution Counts" and "Synthetic Test Data Storage".

Synthetic Test Execution Counts:

When synthetic test tasks are enabled and test results are returned through the synthetic test nodes provided by Guance, the number of new synthetic test data entries within each hour is counted at hourly intervals (per 10,000 API Tests/day).

Each Browser Test execution counts as 10 executions, and each execution of other synthetic test types counts as 1 execution. When self-hosted synthetic test nodes are used, billed executions are calculated at 1/10 of public synthetic test nodes: each Browser Test execution is billed as 1 execution, and each execution of other synthetic test types is billed as 0.1 executions.

Synthetic Test Data Storage:

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

Triggers¶

Counts the total number of scheduled task executions per day based on monitors, AI Monitors, Smart Monitoring, SLOs, Generate Metrics, etc., plus officially provided advanced function execution calls and DataKit or OpenAPI query calls (per 10,000 calls/day).

Calculation Examples¶

1. Standard case: run 1 "sudden change detection" → 5 triggers

2. Exceeding the detection interval: run 1 "outlier detection" with a 30-minute detection interval → base 5 + excess (30-15=15 minutes, 15/15=1) → 6 triggers in total

3. Multiple detections and exceeding the interval: run 2 "interval detections" with a 60-minute detection interval → base 2×5=10 + excess (60-15=45 minutes, 45/15=3) → 13 triggers in total

Data Forwarding¶

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

Sensitive Data Scanning Volume¶

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

If a log entry A needs to be scanned and all three fields within that entry require masking rule processing, the system bills the masking scans for the three fields separately.

Security Detection Scanning Volume¶

Counts the size of data actually scanned by security detection rules each day (compressed) (per GB/day).

Error Records¶

Counts the number of new linked error data entries per day, including error data reported to Error Tracking (per 1,000 entries/day).

Scheduled Reports¶

Counts the number of scheduled reports sent per day in the Workspace (per send/day).

Central Pipeline¶

Counts the log data volume actually processed by the Central Pipeline each day (per GB/day).

SMS¶

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

Phone Calls¶

Counts the number of voice notifications sent each day (per call/day).

Obsy AI¶

Obsy AI Service Subscription¶

Counts the plan tier and subscription fee of the Obsy AI service in the Workspace.

Billing cycle: the activation date serves as the anchor date of the subscription cycle, and the subscription renews automatically on the same day each month. If that date does not exist in a month, renewal occurs on the last day of that month, without changing the original cycle anchor date for subsequent months. For example: activated on January 31, renews on February 28/29, and still renews on March 31.

Plan Upgrades

When users upgrade the Obsy AI service plan, no manual review is required. If the Workspace balance is sufficient, the system immediately deducts the fee and generates a bill, and the plan entitlement and plan bonus credits take effect at the same time.

Bonus Credits

By Credits¶

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

AI Monitor credit consumption: each time a detection runs, Credits are deducted based on the actual consumption of that detection. The configured "Credit Budget per Detection" is used to control the credit consumption of a single detection and does not mean a fixed amount is deducted each time. Each detection is additionally counted as 1 Trigger.

AI Smart Monitoring credit consumption: each time a detection runs, Credits are deducted based on the actual consumption of the AI analysis; each detection is additionally counted as 100 Triggers.

Billing method: Obsy AI Credits use a prepaid top-up model (pay first, use later); pay-as-you-go or postpaid settlement is not supported. 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 rules: the system first uses plan bonus credits for deduction. After plan credits are used up or expire, prepaid Credits are then deducted. Prepaid Credits do not expire; when the credit balance is used up, Obsy AI Q&A, Agent invocation, and other related services can no longer be used until you top up.

Credits Unit Prices

Usage Analysis¶

In Plans & Billing > Usage Analysis, the Commercial Plan "Log Raw Write Traffic (Bytes)" chart is displayed split by log index, and the statistic names use the count("Index") format, where Index is the log index name.

Further Reading¶

You may also want to read: