Tracing Analysis

Tracing Analysis allows developers quickly identify root causes and analyze performance bottlenecks for distributed applications.

Billing Details for Tracing Analysis

Billing Details

Tracing Analysis adopts the pay-as-you-go billing method. You are not charged for activating the service. You are charged only for the volume of data that you submitted. You are not charged for the tracing data in Log Service.

Billing Details (Pay-as-you-Go)
Billable item Free quota Unit price in the Chinese mainland regions (USD/1 million traces per day) Unit price in the China (Hong Kong) region (USD/1 million traces per day) Unit price in the regions outside the Chinese mainland (USD/1 million traces per day)
Computing fee for traces 100,000 traces per day 0.13 0.182 0.182
Storage fee of traces 100,000 traces/day 0.03 0.042 0.042
Storage fee for metrics 1 million metrics per day 0.0015 0.0021 0.0021

Note:
1. Computing Fee of Traces: The fee is calculated based on the number of reported traces. The reported traces are aggregated to generate the metrics of applications, APIs, and databases. The metrics include the consumed time, queries per second (QPS), and the number of exceptions. You can set the sample rate in the Tracing Analysis console to modify the number of traces that can be reported.
Example: 11,000,000 traces are reported every day in a Chinese mainland region. If the free quota is 100,000 traces per day, the fee for the traces is calculated based on the following formula: 11 × USD 0.13 = USD 1.43

2. Storage Fee for Traces: The fee is generated by one million traces.
Example: 1,100,000 traces are reported every day in a Chinese mainland region. The free quota is 100,000 traces per day. The storage duration is 15 days. The total number of stored traces is calculated based on the following formula: 15 (days) × 1 (1 million traces) = 15. In this case, the fee for the traces is calculated based on the following formula: 15 × USD 0.03 = USD 0.45

3. Storage Fee for Traces: The fee is generated by one million traces. Metrics, such as the request data, response time, and the number of exceptions, are the statistical data of applications, APIs, and databases.
Example: 2 million traces are reported every day in a Chinese mainland region. The traces generate approximately 2 million metrics. The free quota is 1 million metrics per day. The storage duration is 15 days. The total number of stored metrics is calculated based on the following formula: 15 × 1 (1 million metrics) = 15. In this case, the total fee is calculated based on the following formula: 15 × 1 (1 million metrics) × USD 0.0015 (unit price) = USD 0.0225.

4. Traces: All spans with the same trace ID in an Alibaba Cloud account are considered to be one request. A request can contain a maximum of 10 spans. For each excess span, you are charged one-tenth of the fee for a request. The size of each span cannot exceed 2 KB. If the size of a span exceeds 2 KB, the excess is discarded.

5. Billing Rules: You are billed for using Tracing Analysis on a daily basis. A bill that contains the costs of the previous day is generated at 00:00:00 (midnight) every day. The fee for the read and write traffic of traces and the aggregation of traces are calculated based on the number of reported traces each day. The storage fee for traces or metrics is calculated based on the total number of stored traces or metrics. The total number is calculated based on the following formula: number of daily stored traces or metrics × storage duration. You can adjust the storage duration in the cluster configurations. The fee quota is reset to a specified value each time a daily bill is generated. If the daily usage is less than the free quota, you are not charged.

Benefits
Number of nodes Number of requests per day Server configurations Cost of open source services (USD/month) Pricing for Tracing Analysis (USD/month)
Small-Sized Businesses Up to 80 nodes 20 million requests. Request complexity: 5 spans per request on average. 4 Elasticsearch instances. Specifications of each instance: a CPU of 4 cores, a memory of 16 GB, and an SSD of 1 TB.
4 Collector servers. Specifications of each server: a CPU of 4 cores and a memory of 8 GB.
864.52 113.29
Medium-Sized Businesses Up to 300 nodes 300 million requests. Request complexity: 7 spans per request on average. 8 Elasticsearch instances. Specifications of each instance: a CPU of 8 cores, a memory of 16 GB, and an SSD of 6 TB.
4 Collector servers. Specifications of each server: a CPU of 4 cores and a memory of 8 GB.
3330.07 2379.79
Large-Sized Businesses Up to 1,000 nodes. 1 billion requests. Request complexity: 8 spans per request on average. 12 Elasticsearch instances. Specifications of each instance: a CPU of 16 cores, a memory of 64 GB, and an SSD of 21 TB
16 Collector servers. Specifications of each server: a CPU of 4 cores and a memory of 8 GB.
9641.81 9599.15
Remarks Each trace can report data that is 10 KB in size based on the Apache documentation. All statistical data is stored for 15 days and full detail data is stored for 7 days. You are charged based on the total number of requests stored for your application. The total number of requests is equal to the number of requests per day multiplied by the request duration. Open-source agents are used. All components (except for agents) are maintained by Alibaba Cloud.

Billing Examples

The following examples are based on the regions in the Chinese mainland.

Case 1: 400 million requests that contain 4 billion spans are reported per day.

Solution 1: The traces and metrics are stored for 30 days.
Fee for the read and write traffic and aggregation of traces:
400 (400 million traces) × USD 0.13 (price for every 1 million aggregate calculations) = USD 52

Daily storage fee for traces:
Stored traces × Unit price = 400 (400 million traces) × 30 (days) × USD 0.03 (price for every 1 million traces) = USD 360

Daily storage fee for metrics:
Stored metrics × Unit price = 400 (400 million metrics generated by 400 million traces) × 30 (days) × USD 0.0015 (price for every 1 million metrics) = USD 18

Total fee: USD 430

Solution 2: Store the traces for seven days and store the metrics for 30 days.

Fee for the read and write traffic and the aggregation of traces:
400 (400 million traces) × USD 0.13 (price for every 1 million aggregate calculations) = USD 52

Storage fee for traces:
Stored traces × Unit price = 400 (400 million traces) × 7 (days) × USD 0.03 (price for every 1 million traces) = USD 84

Storage fee for metrics:
Stored metrics × Unit price = 400 (400 million metrics generated by 400 traces) × 30 (days) × USD 0.0015 (price for every 1 million metrics) = USD 18

Total fee: USD 154

Case 2: 10 million requests that contain 100 million spans are reported per day.

Solution: The traces are stored for seven days, and the metrics are stored for 30 days.

Fee for the read and write traffic and aggregation of traces:
10 (10 million traces) × USD 0.13 (price for every 1 million aggregate calculations) = USD 1.3

Storage fee for traces:
Stored traces × Unit price =10 (indicates 10,000,000 traces) × 7 (days) × USD 0.03 (price for every 1 million traces) = USD 2.1

Storage fee for metrics:
Stored metrics × Unit price = 10 (10 million metrics generated by 10 million traces) × 30 (days) × USD 0.0015 (price for every 1 million metrics) = USD 0.45

Total fee: USD 3.85

wave
phone Contact Us