What Is the LTS Pricing?

Below is a description of the LTS pricing. For specific unit prices, see LTS Pricing Details.

Relationship between the raw log traffic, index traffic, and read/write traffic:
Log read/write: LTS charges for the amount of compressed log data read from and written to LTS. Usually, the log compression ratio is 5:1, indicating that the raw log traffic is five times the read/write traffic.

Example: For 10 GB of raw logs, the compressed size is 2 GB, and 2 GB is billed.

Before the field indexing function is available, all LTS fields support indexing. The index traffic is equal to the raw log traffic. After the field indexing function is available, the index traffic depends on your indexing configuration. If full-text indexing is enabled or no index is configured, the index traffic is equal to the raw log traffic. If only field indexes are configured, only the traffic of fields with indexing enabled is counted.
Log index: Raw logs are full-text indexed by default for log search. Index creation will generate fees.
For example, if the raw logs are 10 GB in size, the amount of data used for indexing is 10 GB and the index traffic fee is $0.8 USD.
Log retention: Space used for retaining compressed logs, indexes, and copies is billed. The space is roughly the size of the raw logs.
For example: If the size of raw logs is 10 GB, the daily retention fee will be at most $0.000125 USD/GB-hour x 24 hours x 10 GB = $0.03 USD.
Differences between ICAgent structuring parsing and cloud structuring parsing:
- ICAgent structuring parsing supports combined parsing based on plug-ins. You can set multiple collection configurations with different structuring parsing rules for a single log stream. You can also choose whether to upload raw logs. If you choose not to upload raw logs, the content field is excluded from resource statistics and billing. This parsing mode is recommended.
- Cloud structuring parsing retains the content field after structuring raw logs. Both the content field and structured fields are included in resource statistics and billing. This parsing mode consumes the computing power of LTS backend. In the future, log processing traffic will be charged based on log size.