Commercial Plan Billing Logic¶

TrueWatch Commercial Plan uses a pay-as-you-go model, with workspaces as the billing unit. The billing cycle is calculated daily, settling data from the previous calendar day at midnight, and the bill is synchronized to the Billing Center.

Settlement Process¶

1. The data volume generated by each service within a workspace is calculated independently.
2. Billing details are generated based on the measured traffic.

3. Billing data is synchronized to the Billing Center, and deductions are made according to the selected payment method.

   • Direct settlement in the Billing Center (top-up, prepaid card)
   • Cloud provider deduction settlement (Huawei Cloud, Alibaba Cloud, AWS, Azure)

Concepts¶

Billing Items¶

Time Series¶

Counts the number of tag combinations for each metric reported by users via DataKit on a given day (per thousand items/day).

For more details, see Time Series Logic Explanation.

Metric Points¶

Full count of all metric data points reported during the storage period (per ten million data points).

Logs¶

Provides corresponding billing methods based on feature usage and storage method.

Standard Storage¶

By default, billing is based on "Number of Log Data Entries". If you prefer to use the "Ingested Traffic" billing model, please contact your account manager.

Billing by Number of Data Entries¶

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

Billing by Ingested Traffic¶

Counts the raw log write traffic size reported by users (before compression, per GB/day).

Long-term Storage¶

The long-term log storage billing volume is calculated based on the raw storage size of log data within the current total long-term storage period, deducting the raw storage size of log data within the standard storage period (per GB/day). That is, only log data exceeding the standard storage duration is billed.

Index Matching¶

Counts the average daily data volume processed by users through index matching (GB/day).

Traces¶

The system intelligently selects the billing method based on actual statistics:

• If Trace count ≥ Span count / 10, billing is based on the number of Traces;
• Otherwise, billing is based on the number of Spans.

Profiling¶

Counts the number of reported Profiling data entries (per ten thousand entries/day).

RUM PV¶

Counts the number of page views reported by users (per ten thousand PV/day).

Session Replay¶

Counts the number of session_id with has_replay: true (per thousand Sessions/day).

Network¶

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

Synthetic Tests¶

There are two billing items for Synthetic Tests: "Synthetic Test Execution Count" and "Synthetic Test Data Storage".

Synthetic Test Execution Count:

When a Synthetic Test task is enabled and returns results through the synthetic test nodes provided by TrueWatch, the number of newly added test data entries is counted hourly (per 10,000 API Tests/day).

Each Browser Test execution counts as 10 executions, while other test types count as 1 execution per execution. When using self-hosted nodes, the billing count is 1/10 of that for public nodes: Browser Test executions count as 1 per execution, and other test types count as 0.1 per execution.

Synthetic Test Data Storage:

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

Triggers¶

Counts the total daily number of executions of scheduled tasks based on Monitors, Intelligent Monitoring, SLOs, Generate Metrics, etc., advanced function execution calls provided by the official platform, and DataKit or OpenAPI query calls (per ten thousand times/day).

Calculation Examples¶

1. Standard Case: 1 execution of "Change Detection" → 5 trigger calls

2. Exceeding Detection Interval: 1 execution of "Outlier Detection", detection interval 30 minutes → Base 5 times + excess portion (30-15=15 minutes, 15/15=1) → Total 6 times

3. Multiple Checks with Excess Interval: 2 executions of "Interval Detection", detection interval 60 minutes → Base 2×5=10 times + excess portion (60-15=45 minutes, 45/15=3) → Total 13 times

Data Forwarding¶

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

Sensitive Data Scanning Traffic¶

Based on scanning rules, the size of raw traffic scanned for sensitive data (per GB/day).

If a log data entry A needs to be scanned, and masking rules need to be applied to three fields within that data, the system bills for the masking scan of each of these three fields separately.

Security Check Scanning Traffic¶

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

Error Records¶

Counts the number of newly added error data entries per day, including error data reported to the Error Center (per 1,000 entries/day).

Scheduled Report¶

The number of daily scheduled report deliveries within the workspace (per delivery/day).

Central Pipeline¶

Counts the data size of all raw logs processed by the central Pipeline (per GB/day).

SMS¶

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

Voice Call¶

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

TOBY AI¶

TOBY AI Service Subscription¶

Counts the plan tier and subscription fee of the TOBY AI service within the workspace.

Billing Cycle: The activation date is the subscription cycle base date, with automatic renewal 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 base date for subsequent months. Example: Activated on January 31, renewed on February 28/29, still renewed on March 31.

Plan Upgrade

When a user upgrades the TOBY AI service plan, no manual review is required. If the workspace balance is sufficient, the system will immediately deduct the fee and generate a bill. Plan benefits and plan-granted credits take effect simultaneously.

Plan-Granted Credits

By Credits¶

Counts the total Credits consumed by TOBY AI Agents and TOBY AI TruePilot on a given day (per 10 Credits/day).

Billing Method: TOBY AI Credits use a prepaid top-up model, not pay-as-you-go or postpaid. Users need to contact their account manager to purchase and top up Credits at the unit price corresponding to the current site and currency.

Deduction Rule: The system first deducts plan-granted credits. After plan-granted credits are used up or expire, prepaid credits are deducted. Prepaid credits do not expire. When the credit balance is exhausted, services such as TOBY AI Q&A and Agent calls will be unavailable until credits are topped up.

Credits Unit Price

Further Reading¶

You may also be interested in: