Billing Plan¶

Includes all billing items and pricing models of Guance, helping you fully understand the product prices of Guance and get a head start on cloud costs.

Billing Items¶

All billing items of Guance are billed separately, for example, log data reported by you will incur log storage fees, and application performance trace data reported by you will incur application performance Trace-related fees.

Sensitive Data Scan Traffic¶

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

For example: If you need to scan a log data A, and each of the three fields in this data requires desensitization rule processing, then the desensitization scanning of these three fields will be billed separately.

When settling in Renminbi:

When settling in US dollars:

SIEM Scan Volume¶

When settling in Renminbi:

When settling in US dollars:

Scheduled Reports¶

That is, the number of scheduled reports sent daily within the workspace (each time/day).

When settling in Renminbi:

When settling in US dollars:

Time Series¶

That is, used to count the number of tag combinations corresponding to all metrics in the metric data reported through DataKit by users on that day (per thousand/day).

When settling in Renminbi:

When settling in US dollars:

Logs¶

Billing by Number of Data Entries¶

That is, data generated from functions such as logs, events, security checks, synthetic tests (per million entries/day).

When settling in Renminbi:

When settling in US dollars:

Billing by Ingested Traffic¶

That is, the size of the raw log ingestion traffic reported by users (per GB/day).

Note: Log data is billed by default according to the number of entries. To switch to billing by ingestion traffic, please contact your account manager.

When settling in Renminbi:

When settling in US dollars:

Data Forwarding¶

Based on the type of external archiving for different data forwarding in the current workspace, the forwarded traffic size is summarized, and daily incremental data is counted and billed accordingly (per GB/day).

When settling in Renminbi:

When settling in US dollars:

Based on the internal storage type of Guance for data forwarding in the current workspace, the forwarded traffic size is summarized, and full data is counted and billed accordingly (per GB/day).

When settling in Renminbi:

When settling in US dollars:

NETWORK¶

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

When settling in Renminbi:

When settling in US dollars:

APM Traces¶

Counts the number of Traces in the reported chain data, generally if Span data has the same trace_id, these Spans will be categorized under one Trace (per million Traces/day).

When settling in Renminbi:

When settling in US dollars:

APM Profiles¶

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

When settling in Renminbi:

When settling in US dollars:

RUM PV¶

Counts the number of page views from user access reported, usually derived by counting the daily Resource, Long Task, Error, Action data (per ten thousand PVs/day).

Note: Whether it's SPA (Single Page Application) or MPA (Multi Page Application), each visit to a page (including refresh or re-entry) counts as 1 PV.

When settling in Renminbi:

When settling in US dollars:

SESSION REPLAY¶

Counts the number of Sessions with actual session replay data. Usually derived by counting the number of session_id where has_replay: true exists in the Session data (per thousand Sessions/day).

When settling in Renminbi:

When settling in US dollars:

Synthetic Tests¶

That is, the cost incurred by using the Synthetic Tests function (per ten thousand API tests/day).

When settling in Renminbi:

When settling in US dollars:

Triggers¶

That is, the cost incurred by using anomaly detection, generating metrics and other functions (per ten thousand times/day).

When settling in Renminbi:

When settling in US dollars:

SMS¶

Counts the number of SMS messages sent on that day (per ten messages/day).

When settling in Renminbi:

Central Pipeline¶

Counts the size of all raw log data hitting the central pipeline processing (per GB/day).

When settling in Renminbi:

When settling in US dollars:

SIEM Scan Volume¶

When settling in Renminbi:

When settling in US dollars:

Scheduled Reports¶

That is, the number of scheduled reports sent daily within the workspace (each time/day).

When settling in Renminbi:

When settling in US dollars:

Time Series¶

That is, used to count the number of tag combinations corresponding to all metrics in the metric data reported through DataKit by users on that day (per thousand/day).

When settling in Renminbi:

When settling in US dollars:

Logs¶

Billing by Number of Data Entries¶

That is, data generated from functions such as logs, events, security checks, synthetic tests (per million entries/day).

When settling in Renminbi:

When settling in US dollars:

Billing by Ingested Traffic¶

That is, the size of the raw log ingestion traffic reported by users (per GB/day).

Note: Log data is by default billed according to the number of entries. To switch to billing by ingestion traffic, please contact your account manager.

When settling in Renminbi:

When settling in US dollars:

Data Forwarding¶

Based on the current workspace's different external archiving types for data forwarding, it summarizes and forwards the traffic size, counts the daily incremental data, and bills accordingly (per GB/day).

When settling in Renminbi:

When settling in US dollars:

Based on the current workspace's data forwarding to Guance internal storage type, it summarizes and forwards the traffic size, counts the full data, and bills accordingly (per GB/day).

When settling in Renminbi:

When settling in US dollars:

NETWORK¶

The number of hosts reporting network data within the workspace (per host reporting network data/day).

When settling in Renminbi:

When settling in US dollars:

APM Traces¶

Counts the number of Traces in the reported chain data, generally if Span data has the same trace_id, these Spans will be categorized under one Trace (per million Traces/day).

When settling in Renminbi:

When settling in US dollars:

APM Profiles¶

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

When settling in Renminbi:

When settling in US dollars:

RUM PV¶

Counts the number of page views from user access reported, usually derived by counting the daily Resource, Long Task, Error, Action data (per ten thousand PVs/day).

Note: Whether it's SPA (Single Page Application) or MPA (Multi Page Application), each visit to a page (including refresh or re-entry) counts as 1 PV.

When settling in Renminbi:

When settling in US dollars:

SESSION REPLAY¶

Counts the number of Sessions with actual session replay data. Usually derived by counting the number of session_id where has_replay: true exists in the Session data (per thousand Sessions/day).

When settling in Renminbi:

When settling in US dollars:

Synthetic Tests¶

That is, the cost incurred by using the Synthetic Tests function (per ten thousand API tests/day).

When settling in Renminbi:

When settling in US dollars:

Triggers¶

That is, the cost incurred by using anomaly detection, generating metrics and other functions (per ten thousand times/day).

When settling in Renminbi:

When settling in US dollars:

SMS¶

Counts the number of SMS messages sent on that day (per ten messages/day).

When settling in Renminbi:

Central Pipeline¶

Counts the size of all raw log data hitting the central pipeline processing (per GB/day).

When settling in Renminbi:

When settling in US dollars: