What Are the Fee Changes for Read/Write, Index, and Storage Traffic of Cloud Structuring?

The fee changes are summarized as follows:

1. LTS structuring types:
   • Cloud structuring parsing: LTS backend uses different log extraction modes to structure the content field of logs in log streams, retaining the content field after structuring. 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.
   • ICAgent structuring parsing: uses user nodes' resources to structure data on the collection side during collection and reports structured data to LTS. 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. For details, see ICAgent structuring parsing rules.
2. Example for reference:

   In a raw log:

   Value of content is "172.16.0.1 200 190 /check"

   After cloud structuring parsing:

   {"ip":"172.16.0.1","status":200,"cost_time":190,"url":"/check","content":"172.16.0.1 200 190 /check"}

3. Fee changes in read/write traffic, index traffic, and storage traffic:

   With the commercial use of ICAgent structuring parsing, storage, index, and read/write traffic for all fields of cloud structuring parsing are now subject to charges.

   • Before the commercial use of ICAgent structuring parsing: LTS backend supported the storage and search of raw logs and structured fields without charges for the storage, index, and read/write traffic of the ip, status, cost_time, and url fields and their values. Only the storage, read/write, and index traffic of the content field and its value are charged.
   • After the commercial use of ICAgent structuring parsing: You will be billed for the storage, index, and read/write traffic of log streams created after ICAgent structuring parsing is put into commercial use. Therefore, in this example, you will be billed for the storage, read/write, and index traffic of the ip, status, cost_time, url, and content fields and their values.