tencent cloud

Tencent Cloud Observability Platform

DocumentationTencent Cloud Observability PlatformPurchase GuideTerminal Performance Monitoring ProBilling Overview

Billing Overview

Download
Focus Mode
Font Size
Last updated: 2026-08-20 18:09:20
AI-Translated
RUM Pro supports the prepaid resource pack billing method. After purchasing a prepaid resource pack, users need to bind it to applications under a specific business system for use.

Billing Description

RUM Pro supports event volume packages and monthly active packages as two billing items.
Package Type
Package Specifications
Validity period
sampling policy
Package deduction
Event Volume Package
Event Volume Package has the following specifications:
600 million, 1.5 billion, 3 billion
1 year
No feature sampling rate limitations; users can configure independently.
Deductible event volume consumption = (sum of (reported quantity per event type × corresponding coefficient)), deducted based on actual consumption. For event types and their corresponding coefficients, see package details.
Settlement: Resource consumption of applications is settled daily. Specifically, the actual usage generated each day is settled starting at 00:00 the next day, with the usage deducted from the bound prepaid resource pack. When the resource pack balance is insufficient to offset the usage, the application enters an overdue payment state. See Overdue Payments.
Monthly Active Package
Monthly Active Package has the following specifications:
MAU 50K, 100K, 200K, 500K, 1M, 2M, 5M, 10M, 15M, 20M
1 year
No feature sampling rate limitations; users can configure independently.
[Deduction] The Monthly Active Package is deducted based on the number of monthly active devices. Any unused resources purchased during the validity period will not be refunded or carried forward.
Settlement: The MAU of applications is updated daily. The actual MAU usage generated in the current month will be settled collectively on the 1st of the following month, with the MAU consumption deducted from the bound prepaid resource pack. When the resource pack balance is insufficient to offset the usage, the application enters an overdue payment state. See Overdue Payments.
Note:
Validity Period: The 1-year validity period is calculated as 365 days. The package takes effect upon activation and expires when either the package event volume is consumed or the validity period ends, (whichever comes first).
Resource packs are prepaid and take effect immediately upon purchase. The validity period of a resource pack is calculated from the actual purchase date.
Resource packs can be bound to multiple applications. During usage settlement, consumption is settled in the order of applications specified by the platform.
Binding multiple prepaid resource packs to an application is supported. During platform settlement, the pack with the shortest validity period is prioritized for deduction. Event Volume Packages and Monthly Active Packages cannot be bound simultaneously.
Unused resources purchased during the validity period will not be refunded or carried forward.
When binding a resource pack to a specified application, if the product is in an overdue payment state, the overdue amount will be settled first. The remaining usage will be settled according to the settlement logic of the corresponding package.

Resource Package Pricing

Event Volume Package

Reporting Quota (entries/year)
list price (USD/year)
Refer to MAU
600 million
9,600
200,000
1.5 billion
24,000
500 thousand
3 billion
48,000
1 million

Monthly Active Package

MAU
list price (USD/year)
Annual MAU Total
50,000
15,000
600,000
100,000
24,000
1.2 million
200,000
39,000
2.4 million
500 thousand
72,000
6,000,000
1 million
105,000
12,000,000
2 million
144,000
24,000,000
5 million
225,000
60,000,000
10 million
300,000
120,000,000
15 million
360,000
180,000,000
20 million
450,000
240,000,000

Package details

APP Monitoring

Event Volume Package

Event types and their corresponding coefficients are defined as follows:
Feature Module
Reporting Item
Coefficient
Description
DAU/PV
DAU/PV
0.1
-
Crash
crash case
100
-
Crash
crash attachment (Android)
200
-
Crash
Custom file
1000
Maximum file size: 2MB
ANR(Android)
ANR case
100
-
ANR(Android)
ANR attachment
200
-
ANR (iOS)
ANR case
500
-
OOM(Android)
OOM case
100
-
FOOM(iOS)
FOOM case
100
-
Error
Exception case
100
-
Error
Custom file
1000
Maximum file size: 2MB
Lag
Lag metrics (Suspension rate & FPS)
1
-
Lag
Lag Instances
50
-
Memory
Memory metrics (Peak memory)
1
-
Memory
Large memory allocation (iOS)
1
-
Memory
VC leak (iOS)
1
-
Memory
Memory graph (iOS)
2000
-
Memory
Java memory leak (Android)
2000
-
Memory
FD peak (Android)
2000
-
Memory
Native memory ceiling (Android)
200
-
Memory
Large bitmap monitoring (Android)
1
-
Launch
Launch Metrics
1
-
Metrickit(iOS)
Metrickit Metrics (iOS)
1
that is a MXMetricPayload data
Metrickit(iOS)
Metrickit individual case (iOS)
200
that is a MXDiagnosticPayload data
Traffic
traffic metrics
1
-
Traffic
Abnormal Traffic Case
50
-
Network
Network reports a record
0.1
that is a network request detail
Battery (Android)
Battery Metrics (Android)
1
-
Battery (Android)
Abnormal Battery Case (Android)
50
-
Log
Log
100
-
Note:
The reporting volume refers to the total amount of data collected by RUM Pro, updated daily based on backend statistics.
Users can view the usage of the reporting quota in the RUM Pro product backend and use the feature switches and sampling rates provided by the product to adjust the reporting volume of different features.
Reporting quotas are bound to applications, allowing multiple applications to be bound to a single resource package, and also allowing a single application to be bound to multiple resource packages.
The product's used reporting volume = sum of (reported quantity per event type × coefficient of the corresponding reporting type).
During the product iteration of RUM Pro, new features may be added. During the validity period of the agreement, the addition of new features will not affect the features already included in your purchase. New features will be equipped with toggles, allowing you to enable relevant features through toggle and sampling configurations. Data collection and reporting resulting from enabling these features will be counted towards the total reporting quota based on the reporting coefficient of the new features.

Monthly Active Package

The Monthly Active Package does not involve event volume or event coefficient statistics. It only counts MAU during each service month and is settled uniformly at the beginning of the following month.
Note:
The Monthly Active Package calculates the MAU of the products bound to the package on a monthly basis. If a user binds the package to multiple products, the MAU for that month is the sum of the MAU from each product.
Customers will have fees calculated and deducted on the 1st of each calendar month, starting from the date the service is activated.
If the period from activation to billing is less than a full calendar month, the Monthly Active Users (MAU) to be charged will be calculated as: (Actual usage days / Total days in that calendar month) * User MAU.

Windows Monitoring

Windows only supports event volume packages. The event types and their corresponding coefficients are defined as follows:
Feature Module
Reporting Item
Coefficient
DAU/PV
DAU/PV
0.1
Crash
crash case
100
Error
Exception case
100
Log
Log
100

Flutter monitoring

The Flutter platform only supports event volume packages. Event types and their corresponding coefficients are defined as follows:
Feature Module
Reporting Item
Coefficient
DAU/PV
DAU/PV
0.1
Error
Exception case
100
Lag
Lag metric (Frames Per Second, FPS)
1
Lag
Lag Instances
50
Launch
Launch Metrics
1

Billing Examples

Assume that Company A purchases a 50,000 MAU resource pack on January 1, 2024. The total annual resource pack is therefore 50,000 × 12 = 600,000, with a validity period from January 1, 2024, to January 1, 2025.
If the actual monthly MAU is 60,000, then in the first 10 months, it consumes 60,000 × 10 = 600,000, and subsequent usage requires purchasing a new resource pack.
If in 1 - 7 months, 60,000 MAU are consumed per month, and in 8 - 12 months, 30,000 MAU are consumed per month, then 60,000 × 7 + 30,000 × 5 = 570,000, and the remaining 30,000 resources are non-refundable.






Previous Topic: Payment OverdueNext Topic: Purchase Instructions

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback