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

Settlement Process¶

Independently count the data volume generated by each service within the workspace.
Generate detailed bills based on the counted traffic.
Synchronize billing data to the Billing Center for deduction according to the selected settlement method.
- Direct settlement via Billing Center (Top-up, Prepaid Card)
- Cloud provider deduction settlement (Huawei Cloud, Alibaba Cloud, AWS, 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 retention policy (retention period). Longer retention periods correspond to higher unit prices.
Data Storage	Customizable retention period settings for different data types.

Billing Items¶

Time Series¶

Counts the number of tag combinations corresponding to each metric in the metric data reported via DataKit on that day (per thousand per day).

For more details, refer to Time Series Logic Explained.

Metric Points¶

Usage Notice

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

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 methods.

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 Traffic", please contact your account manager.

Billing by Data Entries¶

Counts the number of newly reported data entries daily, including data generated by logs, events, Synthetic Tests, and other functions (per 1 million entries per day).

Data Type	Scope	Storage Policy Association
Logs	Daily data increment	When "Custom Multi-Index" is enabled, each index is counted independently, applying the unit price of its corresponding storage policy.
Events	Events generated by monitors, SLOs, Intelligent Inspection, 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 `default` index unit price.

Large Log Splitting Rules

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

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

Billing by Ingested 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 traffic, please contact your account manager.

Long-term Storage¶

Counts the total original storage volume (full amount) of log data within the current long-term storage total period. The 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 amount of log data from 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 count.

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 deduplication of `trace_id`
Span	Per ten million per day	Counts the number of new Spans added that day

APM Profile¶

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

Billing Notice

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. Billing entry calculation formula: Billed Entries = File Size / 300 KB
If the analysis file ≤ 300 KB, it is billed as 1 entry.

RUM PV¶

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

Warning

The larger value between PV Count and PV Count / 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 with has_replay: true (per thousand Sessions per day).

Long Session Splitting

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

If Session time_spent > 4 hours, Billed 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¶

Counts the number of new synthetic test data entries per hour for enabled synthetic test tasks that return results via Guance provided test nodes (per ten thousand API Tests per day).

Query Conditions

Since synthetic test data is currently stored in the log's default index, DQL queries or statistics need to add the following filter conditions:

index = ['default'], source = ['http_dial_testing','tcp_dial_testing','icmp_dial_testing','websocket_dial_testing']

Triggers¶

Costs incurred by using features like anomaly detection, metric generation, etc. (per ten thousand times per day).

Task Type	Billing Rule	Description
Monitor Detection (Standard)	1 time/detection	Other detection types except for Sudden Change, Range, Outlier, and Log Detection
Monitor Detection (Complex)	5 times/detection	Sudden Change 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 overlapped and rounded up per 15 minutes.
Intelligent Monitoring (Host/Log/Application)	10 times/execution	Each execution of detection
Intelligent Monitoring (User Access)	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 advanced functions are selected
Escalation Policy Notification	100 times/trigger	Recorded when an escalation policy is triggered and a notification is sent

Calculation Examples¶

Standard Case: Execute 1 "Sudden Change Detection" → 5 Trigger calls.
Exceeding Detection Interval: Execute 1 "Outlier Detection" with a 30-minute detection interval → Base 5 times + Overlap portion (30-15=15 minutes, 15/15=1) → Total 6 times.
Multiple Detections with Exceeding Interval: Execute 2 "Range Detections" with a 60-minute detection interval → Base 2×5=10 times + Overlap 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	Summarizes traffic after compression by external archive type, counting daily increments.
Internal Storage	Per GB/day	Summarizes traffic original, uncompressed by internal storage type, counting the full amount.

Sensitive Data Scanning Traffic¶

Counts the original traffic size of sensitive data scanned 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 Detection Scanning Traffic¶

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

Error Issue Records¶

Counts the number of newly associated error data entries daily, 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 AI¶

Obsy AI Agent Subscription¶

Counts the number of Obsy AI Agent activations and renewal subscriptions within the workspace (per Agent per month).

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 month, renewal occurs on the last day of that month, without changing the original cycle base date for subsequent months. Example: Activated on Jan 31st, renewal on Feb 28th/29th, March renewal still on March 31st.

Site	Activation Price	Bonus Voucher
China Region	¥999	¥1,000
China Region	$149	$150
China Hong Kong & Global Region	¥2,999	¥3,000
China Hong Kong & Global Region	$399	$400

Voucher Explanation

The special voucher issued upon successful Agent activation/renewal can only be used to offset Credits consumption related to Obsy AI AI. It cannot be used to offset Agent monthly subscription fees, nor can it be withdrawn, transferred, or used to offset other product fees. Vouchers issued for multiple Agents within the same workspace will be aggregated for use. When offsetting, the voucher expiring earliest is consumed first. Vouchers that have expired unused are automatically invalidated.

By Credits¶

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

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

Deduction Rules: The system prioritizes using the earliest expiring, unexpired special voucher within the current workspace for deduction. Any portion exceeding the voucher balance or after vouchers expire is billed on a pay-as-you-go basis.