Billing Items

Description

The billing items of LTS include the log read/write traffic, log index traffic, and log volume. For details, see Table 1.

**Table 1** Billing items
Category	Item	Description	Billing Mode	Free Quota
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
Storage	Log volume	Log volume generated when raw logs (backup and compressed logs) and logs are indexed (uncompressed logs). Example: If 10 GB raw logs are uploaded and the full-text index is enabled, the log volume of raw logs (backup and compressed logs) and indexed logs is 10 GB.	Pay-per-use: Log volume fee = Log volume (GB) x Unit price per GB	500 MB/month

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).

You want to analyze daily logs using LTS for one month. Billing details are shown in the following table.

**Table 2** Billing details (full-text index)
Item	Description	Monthly 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/1024) x 0.05 = $29.98 USD
Index traffic	100 GB x 30 = 3000 GB	3000 GB	$0.08 USD/GB	(3000 GB – 500 MB free quota/1024) x 0.08 = $239.96 USD
Storage space	Log volume = 100 GB/day x 30 days = 3000 GB	3000 GB	$0.000125 USD/GB-hour	(3000 GB – 500 MB free quota/1024) x 0.000125 x 24 hours x 30 days = $269.96 USD