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¶

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

Concepts¶

Term	Description
Basic Billing	The unit price for billing items is a fixed value.
Tiered Billing	The unit price is tied to the data storage policy (retention period). Longer retention periods correspond to higher unit prices.
Data Storage	Customize the retention period for different data types.

Billing Items¶

Time Series¶

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

For more details, refer to Time Series Logic Explained.

Metric Points¶

Usage Notes

If you need to switch from "Time Series" to "Metric Points" for metric billing, please contact your account manager.

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 measured and charged based on "Log Data Entries". If you need to adopt the billing mode based on "Ingested Log Traffic", please contact your account manager.

Billing by 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).

Data Type	Scope of Statistics	Association with Storage Policy
Logs	Daily data increment	When "Custom Multiple Indices" is enabled, each index is counted independently, applying the unit price of its corresponding storage policy.
Events	Events generated by monitors, SLOs, Intelligent Inspection, and custom events.	By default, uses the unit price of the log `default` index's storage policy.
Synthetic Tests (Self-built Nodes)	Synthetic test data reported by self-built test nodes.	Same as above, uses the unit price of the `default` index.

Large Log Splitting Rules

ES Storage: When a single log > 10 KB, Billing Entries = Log Size / 10 KB
SLS Storage: When a single log > 2 KB, Billing Entries = Log Size / 2 KB

A single data entry smaller than the above limits is counted as 1 entry.

Billing by Ingested Log Traffic¶

Counts the size of the original log traffic ingested by the user (before compression, per GB per day).

Warning

To switch to billing by ingested log traffic, please contact your account manager.

Long-term Storage¶

Counts the total original storage volume (full volume) of log data within the current long-term storage total period. The statistical scope includes data within the standard storage period (per GB per day).

Storage Example

Suppose you set the standard storage duration to 30 days and the long-term storage duration to 180 days. Long-term storage billing is calculated based on the full volume of log data within the last 180 days, not just the incremental data from days 31–180. This means data from the last 30 days, which is currently within the standard storage period, is also included in the long-term storage statistics.

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.

Billing Dimension	Unit	Counting Method
Trace	Per million per day	Counted by deduplicated `trace_id`.
Span	Per ten million per day	Counts the number of new Spans added on the day.

APM Profile¶

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

Billing Notes

Profile data mainly consists of two parts: basic attribute data + Profile analysis file.

If the Profile analysis file > 300 KB, the data will be split into multiple entries for billing. The billing entry count formula: Billing Entries = File Size / 300 KB.
If the analysis file ≤ 300 KB, it is counted as 1 entry.

RUM PV¶

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

Billing Notes

The larger value between PV Count and the sum of Resource, Long Task, Error, Action entries / 100 is taken as the daily billing data.

Both SPA (Single Page Application) and MPA (Multi Page Application) are counted based on page access times (including refreshes). Each access counts as 1 PV.

Session Replay¶

Counts the number of session_id where has_replay: true exists (per thousand Sessions per day).

Long Session Splitting

If there is an excessively long active Session, the Session will be split into multiple entries for billing based on time_spent:

If Session time_spent > 4 hours, Billing Count = time_spent / 4 hours.
If time_spent ≤ 4 hours, it is counted as 1 Session.

Network¶

Counts the number of host 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:

When Synthetic Tests tasks are enabled and test results are returned via the test nodes provided by Guance, the number of new test data entries generated within each hour is counted (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, meaning 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 test data entries per day (per million entries per day).

Triggers¶

Counts the total number of daily 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).

Task Type	Billing Rule	Description
Monitor Detection (Standard)	1 time/detection	Other detection types besides anomaly, range, outlier, and log detection.
Monitor Detection (Complex)	5 times/detection	Anomaly detection, range detection, outlier detection, log detection.
Detection Interval Overlap	+1 time/15 minutes	When detection interval > 15 minutes, the portion exceeding 15 minutes is rounded up per 15 minutes and added.
Intelligent Monitoring (Host/Log/Application)	10 times/execution	Each execution of detection.
Intelligent Monitoring (RUM)	100 times/execution	Each execution of detection.
DataKit/OpenAPI Query	1 time/query	-
Metric Generation	1 time/query	Each query when metric generation is enabled.
DataFlux Func Advanced Functions	1 time/query	Each query when an advanced function is selected.
Upgrade Policy Notification	100 times/trigger	Recorded when an upgrade policy is triggered and a notification is sent.
Programmable Monitor/Security Check Rules	100 times/trigger	Each execution of detection.

Calculation Examples¶

Standard Case: Executing 1 "Anomaly Detection" → 5 task triggers.
Exceeding Detection Interval: Executing 1 "Outlier Detection" with a 30-minute detection interval → Base 5 times + exceeding portion (30-15=15 minutes, 15/15=1) → Total 6 times.
Multiple Detections Exceeding Interval: Executing 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 categories of billing.

Forwarding Type	Unit	Counting Method
External Storage	Per GB/day	Aggregates traffic after compression by external archive type, counting daily increments.
Internal Storage	Per GB/day	Aggregates traffic original, uncompressed by internal storage type, counting the full volume.

Sensitive Data Scan Traffic¶

Counts the original traffic size of scanned sensitive data based on scanning rules (per GB per 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 Check Scan Traffic¶

Counts the actual data size scanned by security check rules per day (after compression) (per GB per 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 original log data processed by all Central Pipelines (per GB per 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 subscription cycle starts on the activation date and automatically renews on the same day each month. If that date does not exist in a given month, renewal occurs on the last day of that month, without changing the original cycle start date for subsequent months. For example: Activated on Jan 31st, renewal on Feb 28th/29th, and still renews on Mar 31st for March.

Plan	Supported Agent Count	China Region - RMB	China Region - USD	China Hong Kong & Global Region - RMB	China Hong Kong & Global Region - USD
Free	Up to 1	Free	Free	Free	Free
Pro	Up to 3	¥999	$150	¥1999	$300
Team	Up to 20	¥2999	$450	¥5999	$900

Credits Included

Plan	China Region	China Hong Kong & Global Region	Distribution Rule
Free	2,000 Credits/month	750 Credits/month	Distributed on the 1st of each calendar month, reset monthly, non-cumulative.
Pro	20,000 Credits/month	15,000 Credits/month	Distributed per subscription cycle, automatically added upon successful renewal, does not expire.
Team	-	-	Distributed per subscription cycle, automatically added upon successful renewal, does not expire.

Credits Included Explanation

Credits included with the Free plan are reset on the 1st of each month and do not carry over.
For paid plans, corresponding credits are distributed immediately upon activation. Upon renewal, credits are distributed again based on the new subscription cycle. When upgrading, the credit difference between the old and new plans is supplemented based on the remaining cycle.
Credit calculation results are rounded down to the nearest integer.

Billing by Credits¶

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

Billing Method: The system first calculates Credits consumed based on actual usage, then converts them to fees according to the unit price corresponding to the current site and currency.

Deduction Rule: The system prioritizes using included credits for deduction. After included credits are exhausted, the excess is billed on a pay-as-you-go basis.

Credits Unit Price

Site	Unit Price
China Region	¥0.25
China Region	$0.036
China Hong Kong & Global Region	¥0.7
China Hong Kong & Global Region	$0.1

Note

The unit price above is per 10 Credits.