Billing Items

Description

As shown in Figure 1, the billing items of LTS include the log read/write traffic, log index traffic, log storage volume, and basic and advanced log transfer traffic. For details, see Table 1.

Figure 1 Billing items

**Table 1** Billing items
Category	Item	Description	Billing Mode	Free Quota
Storage	Standard storage volume	Log storage volume of raw logs (including backup logs; compressed). If 10 GB raw logs are uploaded, the storage volume of raw logs (including backup logs; compressed) is 10 GB.	Pay-per-use: Standard storage volume fee = Standard storage volume (GB) x Unit price per GB	500 MB/month
Storage	Cold storage volume	Log storage volume of raw logs (including backup logs; compressed). If 10 GB raw logs are uploaded, the storage volume of raw logs (including backup logs; compressed) is 10 GB.	Pay-per-use: Cold storage volume fee = Cold storage volume (GB) x Unit price per GB	None
Traffic	Log read/write traffic	Includes write traffic and read traffic: Write traffic: When the compressed data is uploaded to LTS, the write traffic is billed based on the amount of transmitted data. For example, if 5 GB data is uploaded to LTS, 1 GB write traffic (compression rate: 20%) will be generated. Read traffic: Read traffic is not counted and is free of charge.	Pay-per-use: Read and write traffic fee = Write traffic (GB, 20% compression rate) x Unit price per GB	500 MB/month
Traffic	Log index traffic	Details are as follows: By default, full-text indexes are created for raw logs. The index traffic is billed based on the index data volume generated by uncompressed logs. Index traffic is billed at a time when data is written, that is, full-text index traffic. For a field for which both a full-text index and a field index are constructed, index traffic is billed only once, that is, full-text index traffic. When the full-text index is disabled and only the field index is enabled, fields of long and float types are not counted in the index traffic. The index traffic occupied by each field value is 8 bytes. If the type is string, the log field name (Key) and field value (Value) are stored as the text type, and the field name and value are included in the index traffic. Field indexes can be used to reduce index traffic fees. Examples: If an index (string type) is set for the request_uri field and the field value is /request/path, both request_uri and /request/path are counted in the index traffic. If an index (long type) is set for the status field and the field value is 400, status is not counted in the index traffic. The index traffic of 400 is 8 bytes. NOTE: This function is now under internal testing by some users. It will be available soon for all users. Examples: If 10 GB raw logs are written and the full-text index is enabled, the 10 GB index traffic is billed. For example, if 10 GB raw logs are written and the index for two fields is enabled, the data volume is 5 GB, and the 5 GB index traffic is billed. If 10 GB raw logs are written and the index for two fields is enabled, the 10 GB index traffic is billed.	Pay-per-use: Log index fee = Index traffic (GB) x Unit price per GB	500 MB/month
Transfer	The open beta test (OBT) of the log transfer function is about to end. From April 30 to June 30, 2024, charging for this function will be gradually enabled in each region. The transfer fee covers only traffic for transferring custom log fields and does not cover that for transferring built-in reserved fields of LTS. Log sample: The raw log is 192.168.0.1 200 190 /check. After being structured, the log becomes {"ip":"192.168.0.1","status":200,"cost_time":190,"url":"/check"}. The following uses this sample to describe how traffic is calculated.
	Basic log transfer traffic	Basic log transfer includes transferring logs in raw or JSON format to Object Storage Service (OBS), and transferring logs to Distributed Message Service (DMS) and Data Ingestion Service (DIS). It does not require field mapping between the source log stream and the transfer destination, consuming less computing power than advanced log transfer. Basic transfer traffic includes the traffic for transferring non-compressed data. Example: If you transfer the raw log to DMS, LTS collects statistics on the size of the log (non-compressed). The transfer traffic is length("192.168.0.1 200 190 /check") = 26 bytes. If you transfer the structured log to DMS, LTS collects the size of the keys and values (non-compressed) in the log. Each number is counted as 8 bytes. Therefore, the transfer traffic is length("ip") + length("192.168.0.1") + length("status") + 8 + length("cost_time") + 8 + length("url") + length("/check") = 2 + 11 + 6 + 8 + 9 + 8 + 3 + 6 = 53 bytes.	Pay-per-use: Basic transfer traffic fee = Transfer traffic (GB, non-compressed) x Unit price per GB	None
	Advanced log transfer traffic	Advanced log transfer includes transferring logs in ORC format to OBS, and transferring logs to Data Warehouse Service (DWS) and Data Lake Insight (DLI). It requires field mapping between the source log stream and the transfer destination, consuming more computing power than basic log transfer. Advanced transfer traffic includes the traffic for transferring non-compressed data. Example: If you transfer the ip, status, cost_time, and url fields in the log to DWS, LTS collects the size (non-compressed) of each field value. Each number is counted as 8 bytes. Therefore, the transfer traffic is length("192.168.0.1") + 8 + 8 + length("/check") = 11 + 8 + 8 + 6 = 33 bytes.	Pay-per-use: Advanced transfer traffic fee = Transfer traffic (GB, non-compressed) x Unit price per GB	None

To avoid extra expenses, you can configure log collection to stop when the quota runs out on the Configuration Center page. For details, see Configuration Center.

Billing Examples

The full-text index application scenario is used as an example.

The prices mentioned in the figure are only for reference. For details, see Price Calculator.

Assume that you have a server generating 100 GB raw logs every day, full-text index is enabled, and logs are retained for 30 days (the earliest logs are deleted first). After you enable intelligent cold storage, data is stored in the standard storage tier for seven days. Therefore, the cold storage duration is 23 days (30 – 7). For details, see the following table.

**Table 2** Billing details (full-text index)
Item	Description	Usage	Unit Price	Monthly Billing
Read/Write traffic	Daily read/write traffic: 100 GB/5 (compression rate) = 20 GB. Accumulated read and write traffic for 30 days: 20 GB x 30 = 600 GB.	600 GB	$0.05 USD/GB	(600 GB – 500 MB/1,024) x 0.05 = $29.98 USD
Index traffic	100 GB x 30 = 3,000 GB	3,000 GB	$0.08 USD/GB	(3,000 GB – 500 MB free quota/1,024) x 0.08 = $239.96 USD
Standard storage	Standard storage volume = 100 GB/day x 7 days = 700 GB	700 GB	$0.000125 USD/GB-hour	(700 GB – 500 MB free quota/1,024) x 0.000125 x 24 hours x 30 days = $62.96 USD
Cold storage	Cold storage volume = 100 GB/day x 23 days = 2,300 GB	2,300 GB	$0.00003993 USD/GB-hour	2,300 GB x 0.0003993 x 24 hours x 30 days = ¥66.12
Basic log transfer traffic	Basic log transfer traffic: 100 GB/day x 30 days = 3,000 GB	3,000 GB	$0.0125 USD/GB	3,000 GB x $0.0125 USD = $37.5 USD
Advanced log transfer traffic	Advanced log transfer traffic: 100 GB/day x 30 days = 3,000 GB	3,000 GB	$0.05 USD/GB	3,000 GB x $0.05 USD = $150 USD