Includes all billing items and pricing models of TrueWatch to help you fully understand the product pricing of TrueWatch and get a head start on cloud costs.
All billing items of TrueWatch are charged separately. For example, the log data you report will incur log storage fees, and the APM trace data you report will incur APM Trace-related fees.
The size of the original traffic of sensitive data scanned based on scan rules (per GB / day).
For example: If log data A needs to be scanned and three fields within this data require desensitization rule processing, the desensitization scan for these three fields will be charged separately.
The data generated by the use of logs, events, security checks, and availability tests (per million / day).
Warning
If the "Custom Multiple Indexes" feature is enabled for logs, the daily data increment will be counted based on different indexes, and the actual cost will be calculated based on the unit price of the corresponding data storage policy;
Events include events generated by monitoring module (monitors, SLO) configuration detection tasks, events reported by intelligent inspections, and events reported by users;
Availability test data reported by self-built test nodes;
The fees for events, security checks, and availability tests are calculated based on the unit price of the "default" index for logs by default.
Based on the different types of external archives for data forwarding in the current workspace, the size of the forwarded traffic is summarized, the daily incremental data is counted, and the billing is based on the corresponding data (per GB / day).
When settled in RMB:
Details
China Region
￥0.35
Details
Hong Kong and Global Regions
￥0.7
When settled in USD:
Details
China Region
$ 0.05
Details
Hong Kong and Global Regions
$ 0.1
Based on the data forwarding to the internal storage type of TrueWatch in the current workspace, the total forwarded traffic is summarized, the full data is counted, and the billing is based on the corresponding data (per GB / day).
The number of Traces in the reported trace data. Generally, if the trace_id in the Span data is the same, these Spans will be classified under one Trace (per million Traces / day).
The number of page views accessed by users, generally calculated by counting the number of Resource, Long Task, Error, and Action data generated daily (per ten thousand PVs / day).
Note: Whether it is SPA (Single Page Application) or MPA (Multi Page Application), each time a user accesses a page (including refresh or re-entry) is counted as 1 PV.
The number of Sessions that actually generated session replay data. Generally calculated by counting the number of session_id with has_replay: true in the Session data (per thousand Sessions / day).