tencent cloud

CLS is a pay-as-you-go service which bills you according to actual resource usage and deduct fees on a daily basis. If an account has overdue payment, CLS will isolate its existing resources, prohibit operations such as log upload and query, and terminate related resources and data 15 days later.

Note：

• CLS was officially commercialized at 00:00:00 on August 3, 2020. After the commercialization, CLS still provides a free tier for all users in each region.
• If you know the resource usage and need to know the cost estimate, use the Price Calculator to export the cost estimate list.

Billing Mode

Billable items

Overview

CLS has the following billable items in different billing modes. The index traffic, log storage, and index storage fees are subject to the log storage class. For more information, see Storage Class Overview.

Billable item in each step of log data processing in CLS are as shown below:

Detailed description

Traffic fees

Storage fees

1. Standard/IA logs and indexes have different storage prices and are billed separately.
2. Storage is billed based on average usage. Storage usage values are collected on each hour, and averaged per day.
3. The log data and index data are saved based on your configured storage cycle. Expired data does not incur storage fees and will be deleted on the hour. For example, assume that the storage cycle is set to 3 days and logs are uploaded at 12:15 on June 15. The logs will be saved between 12:15 on June 15 and 12:15 on June 18, and the expired data will be deleted at 13:00 on June 18. Do not change the storage cycle frequently, and you can only change it once a day.
   • Extending the storage cycle
     When you extend the storage cycle, CLS will save the data for a longer period. For example, if you extend the storage cycle from 7 days to 15 days at 12:30 on June 15, the data uploaded at 12:00 on June 8 will be saved until 13:00 on June 23, instead of being deleted at 13:00 on June 15.
   • Shortening the storage cycle
     When you shorten the storage cycle, CLS will save the data for a reduced period. For example, if you shorten the storage cycle from 15 days to 7 days at 12:30 on June 15, the data uploaded between 12:00 on June 1 and 13:00 on June 8 will be deleted at 13:00 on June 15.

Computing fees

Other fees

The service request and topic partition fees have low unit prices and only account for a very small part of the total fees if you use CLS normally. Such fees are mainly used to prevent abuse such as high numbers of meaningless concurrent API calls.

Billing Examples

NGINX log query and analysis

Company A's website receives 100 million requests per day, and each request produces a 100-byte log on average. This results in 100 million logs per day for a total of approximately 9.31 GB. Company A decides to upload the NGINX access logs to the CLS service in the Beijing region and save them in the STANDARD storage class for 15 days. Log search, analysis, and alarming features are used, while data processing, download, consumption, and shipping features are not used.

As you can see from the billable items, the index traffic and storage fees are the major fees for the following reasons:

• Index is the core of log search and analysis. Log data cannot be searched for if there are no indexes. Therefore, the unit price of the index traffic (0.062 USD/GB/day) is higher than that of the write traffic (0.032 USD/GB/day).
• If logs are compressed when uploaded, the write traffic and log storage capacity will be calculated based on the compressed log data volume, while the index traffic and storage capacity will be calculated based on the data volume of uncompressed raw logs. As the log compression ratio generally ranges from 1:4 to 1:10, the index traffic and storage capacity will be about 4–10 times the write traffic and log storage capacity respectively.

Therefore, to reduce the product costs, you can appropriately adjust the index configuration to reduce the index traffic and storage capacity.

If a raw log is:

10.20.20.10 ::: [Tue Jan 22 14:49:45 CST 2019 +0800] ::: GET /online/sample HTTP/1.1 ::: 127.0.0.1 ::: 200 ::: 647 ::: 35 ::: http://127.0.0.1/

The log will be captured as the following fields during log collection:

IP: 10.20.20.10
bytes: 35
host: 127.0.0.1
length: 647
referer: http://127.0.0.1/
request: GET /online/sample HTTP/1.1
status: 200
time: [Tue Jan 22 14:49:45 CST 2019 +0800]

• If full-text index is enabled, the index generated by the log will be 172 bytes in size (i.e., size of all field keys and values). The index traffic will be generated, and the storage capacity will be used accordingly.
• If you don't enable full-text index and only enable key-value index for the request and status fields, the indexes generated by the log will be 48 bytes in size (i.e., size of the key and value of request and status, which are 48 bytes / 172 bytes = 27.9% of all fields). In this way, the index traffic and storage capacity will be reduced to 27.9% of those for full-text index. However, you can only use the request and status fields to search for and analyze logs and view other fields in this case.

For more methods to reduce product costs, see Saving Product Use Costs.