Docs

Torch Log Service

Billing and cost FAQ

How to view TLS resource usage

This section describes how to view TLS resource usage:

How to view the resource usage overview?

Why is there an order from the Shanghai Region when activating the TLS for the first time?

Does querying and analyzing logs generate read traffic?

Why are the fees for indexing, delivery, and processing traffic several times higher than read/write traffic fees?

Do JSON subfields without an index generate index traffic?

How to view the resource usage overview?

On the TLS console Overview page, you can view usage information for the previous day in the current region under the current account, including log storage volume, index storage volume, write traffic, index traffic, API call count, and more.

Use the cloud monitoring service to view the billing resource usage for a specified log topic. For details, see View cloud monitoring data.

Why is there an order from the Shanghai Region when activating the TLS for the first time?

East China 2–Shanghai is the central Region for TLS. When TLS is enabled for the first time, TLS will automatically create a zero-cost order for the Shanghai Region. The order type is purchase, and the configuration details are TLS Standard Edition–Pay-as-you-go–Shanghai.

You do not need to pay attention to the region of the initial order. Simply ensure that log data is uploaded to the correct target Region.

Does querying and analyzing logs generate read traffic?

TLS supports querying or analyzing logs via the console or API. Neither method generates read traffic or corresponding fees.

Notice

TLS public network read traffic refers to the downstream traffic generated when data is obtained through the TLS public network domain name. This includes actions such as downloading logs via the public network or consuming logs via the public network using a program, all of which generate public network read traffic.

TLS private network read traffic refers to the downstream traffic generated when data is obtained through the TLS private network domain name. This includes actions such as downloading logs via the private network or consuming logs via the private network using a program, all of which generate private network read traffic.

Why are the fees for indexing, delivery, and processing traffic several times higher than read/write traffic fees?

Index traffic, delivery traffic, and processing traffic in TLS are calculated based on the uncompressed data volume, while read/write traffic is calculated based on the compressed data volume. For example, when creating a delivery task, if the original data is 10 GB and the compression rate is 20%, the compressed data volume is 2 GB. Therefore, the delivery traffic is 10 GB, and the read/write traffic is 2 GB.

Do JSON subfields without an index generate index traffic?

JSON subfields without an index in JSON-type fields will generate index traffic.

The specific reasons are as follows:

After creating an index for a JSON-type field, both the field name and field value (including subnodes) will generate index traffic. Among them:

If no index is created for a JSON subfield, the subfield is categorized as the value of a JSON type field. TLS calculates index traffic based on text type.

When JSON subfield is indexed, TLS calculates index traffic based on the data type of subfield, such as text, long, and double type.

Last updated: 2026.06.25 16:38:26