You are separately charged for the billable items of Log Service. For example, if you collect logs, you are charged a write traffic fee. If you store logs, you are charged a log storage fee. This topic describes the billable items of Log Service and the billing method for each item.

Note
  • You can use Log Service to collect log data and time series data. The pricing of stored data and indexes for time series data is different from the pricing of stored data and indexes for log data. However, the pricing of other billable items for time series data is the same as the pricing of other billable items for log data. The billable items include data transformation, data shipping, read and write traffic, and the number of requests.
  • You can view the following statistics of the previous day in the Log Service console: write traffic, read traffic, number of read and write operations, transformation traffic, shipping traffic, and storage space.
  • When you use Log Service to collect log data, the log data is automatically compressed. The compression ratio ranges from 10:1 to 5:1.

The following table shows the billable items of Log Service. For more information about the pricing of Log Service, visit the Log Service pricing page.

Billable item Description Billing detail Free quota
Storage space occupied by log data The storage space is the total size of compressed log data and indexes that are created on raw log data.

For example, the size of raw log data that is uploaded to Log Service is 1 GB, and indexes are created for two fields. The compression ratio is 5:1 when the raw log data is uploaded, and the size of the indexes is 0.5 GB. In this example, the storage space occupied by log data is calculated by using the following formula: 0.2 GB + 0.5 GB = 0.7 GB.

  • Pay-as-you-go: Daily fee of the storage space occupied by log data = Used storage space per day × Price per GB of log data.
  • Resource plan: Purchased resource plans are used to offset the fees of billable items based on the charge units (CUs) of the billable items.
500 MB per month
Notice Free quotas are provided only when you do not use resource plans to offset the fees of consumed resources.
Storage space occupied by cold log data After you enable the hot and cold-tiered storage feature for a Logstore, you can configure the Hot Data Retention Period parameter. If the retention period of hot log data exceeds the specified threshold, the hot log data is converted to cold log data. The storage space is the total size of compressed log data and indexes that are created on raw log data.

For example, the size of raw log data that is uploaded to Log Service is 1 GB, and indexes are created for two fields. The compression ratio is 5:1 when the raw log data is uploaded, and the size of the indexes is 0.5 GB. In this example, the storage space occupied by cold log data is calculated by using the following formula: 0.2 GB + 0.5 GB = 0.7 GB.

  • Pay-as-you-go: Daily fee of the storage space occupied by cold log data = Used storage space per day × Price per GB of log data.
  • Resource plan: Purchased resource plans are used to offset the fees of billable items based on the CUs of the billable items.
None
Storage space occupied by time series data The storage space is the total size of raw time series data and indexes that are created on raw time series data.

For example, the size of raw time series data that is uploaded to Log Service is 1 GB, and indexes are automatically created. In this example, the storage space occupied by time series data is calculated by using the following formula: 1 GB + 1 GB = 2 GB.

  • Pay-as-you-go: Daily fee of the storage space occupied by time series data = Used storage space per day × Price per GB of time series data.
  • Resource plan: Purchased resource plans are used to offset the fees of billable items based on the CUs of the billable items.
None
Read and write traffic Read and write traffic includes write traffic and read traffic.
  • Write traffic: Write traffic is calculated based on the volume of compressed data that is uploaded to Log Service.

    For example, 10 GB of raw data is uploaded to Log Service, and the compression ratio is 5:1. In this example, the write traffic is 2 GB.

  • Read traffic: Read traffic is calculated based on the volume of compressed data that is transformed, shipped to AnalyticDB for MySQL or ApsaraDB for Lindorm, or consumed.

    For example, 10 GB of raw data is uploaded to Log Service and then shipped to ApsaraDB for Lindorm, and the compression ratio is 5:1. In this example, the write traffic is 2 GB when the raw data is uploaded to Log Service, and the read traffic is 2 GB when the uploaded data is shipped to ApsaraDB for Lindorm.

Note When you use the consumption preview feature in the Log Service console, a small amount of read traffic is generated.
  • Pay-as-you-go: Daily fee of read and write traffic = (Write traffic per day + Read traffic per day) × Price per GB of traffic.
  • Resource plan: Purchased resource plans are used to offset the fees of billable items based on the CUs of the billable items.
500 MB per month
Notice Free quotas are provided only when you do not use resource plans to offset the fees of consumed resources.
Index traffic of log data The index traffic is calculated based on the indexes that are created or recreated on raw log data. Indexes are created for fields. The index traffic is based on the lengths of indexed fields and field values.
  • For example, 1 GB of raw log data is written to Log Service, and the full-text indexing feature is enabled. In this example, the index traffic is 1 GB.
  • For example, 1 GB of raw log data is written to Log Service, and indexes are created for two fields whose data length is 0.5 GB. In this example, the index traffic is 0.5 GB.
Note
  • By default, the indexing feature is disabled. If you enable this feature, index traffic is generated, and storage space is occupied by indexes.
  • If you create both a full-text index and a field index for a field, the fee of index traffic for the field is calculated only once.
  • Log Service automatically creates indexes for reserved fields such as __time__ and __source__. This generates a small amount of index traffic. For more information, see Reserved fields.
  • Pay-as-you-go: Daily fee of the index traffic of log data = Index traffic per day × Price per GB of index traffic.
  • Resource plan: Purchased resource plans are used to offset the fees of billable items based on the CUs of the billable items.
500 MB per month
Notice Free quotas are provided only when you do not use resource plans to offset the fees of consumed resources.
Index traffic of time series data The index traffic is calculated based on the indexes that are created on raw time series data. Indexes are created for fields. The index traffic is based on the lengths of indexed fields and field values.

When you upload time series data, Log Service automatically creates indexes on the time series data.

For example, 1 GB of raw time series data is written to Log Service. In this example, the index traffic is 1 GB.

  • Pay-as-you-go: Daily fee of the index traffic of time series data = Index traffic per day × Price per GB of index traffic.
  • Resource plan: Purchased resource plans are used to offset the fees of billable items based on the CUs of the billable items.
None
Read traffic over the Internet
  • If data in Log Service is read and consumed by third-party applications, you are charged for the read traffic over the Internet. The traffic is calculated based on the data after compression.
  • If data is transformed across regions, you are charged for the read traffic over the Internet. The traffic is calculated based on the transformed data after compression.
  • Pay-as-you-go: Daily fee of the read traffic over the Internet = Read traffic over the Internet per day × Price per GB of read traffic over the Internet.
  • Resource plan: Purchased resource plans are used to offset the fees of billable items based on the CUs of the billable items.
None
Data transformation You are charged for the transformed data before compression.
The fee of the data transformation billable item is calculated only based on the size of transformed data. However, the data transformation feature causes other fees.
  • When you transform data, network resources are consumed, and API operations are called to read data. You are charged for the read traffic and the number of read and write operations.
  • If data is transmitted across regions for data transformation, read traffic over the Internet is generated.
  • Pay-as-you-go: Daily fee of data transformation = Transformed data per day × Price per GB of transformed data.
  • Resource plan: Purchased resource plans are used to offset the fees of billable items based on the CUs of the billable items.
None
Data shipping You are charged for the shipped data before compression. You can ship data to Object Storage Service (OSS), AnalyticDB for MySQL, and ApsaraDB for Lindorm.
Note When you ship data to AnalyticDB for MySQL or ApsaraDB for Lindorm, network resources are consumed, and API operations are called to read data. You are charged for the read traffic and the number of read and write operations.
  • Pay-as-you-go: Daily fee of data shipping = Shipped data per day × Price per GB of shipped data.
  • Resource plan: Purchased resource plans are used to offset the fees of billable items based on the CUs of the billable items.
None
Read and write operations
  • When you upload data to Log Service, you are charged for the number of write operations. The number of write operations is based on the speed at which data is generated. Log Service automatically minimizes the number of write operations.
  • When data is transformed, shipped to AnalyticDB for MySQL or ApsaraDB for Lindorm, or consumed, Log Service reads the data in batches. You are charged for the number of read operations.
Note The number of read and write operations includes both successful and failed operations.
  • Pay-as-you-go: Daily fee of read and write operations = Number of read and write operations per day × Price per operation.
  • Resource plan: Purchased resource plans are used to offset the fees of billable items based on the CUs of the billable items.
1 million per month
Notice Free quotas are provided only when you do not use resource plans to offset the fees of consumed resources.
Voice calls When you receive alert notifications by using voice calls, you are charged for the number of times that alert notifications are sent.
Note
  • If a voice call is not answered, Log Service sends a text message.
  • You are charged for a voice call regardless of whether the call is answered. You are not charged for the text message that is sent upon a non-answered voice call.
  • Pay-as-you-go: Daily fee of voice calls = Number of times that alert notifications are sent per day × Price per notification.
  • Resource plan: Purchased resource plans are used to offset the fees of billable items based on the CUs of the billable items.
None
Text messages When you receive alert notifications by using text messages, you are charged for the number of times that alert notifications are sent.
Note If a text message is longer than 70 characters, the text message is split into two messages for sending. In this case, you are charged only for one text message.
  • Pay-as-you-go: Daily fee of text messages = Number of times that alert notifications are sent per day × Price per notification.
  • Resource plan: Purchased resource plans are used to offset the fees of billable items based on the CUs of the billable items.
None
Active shards The fee is calculated based on the number of shards in the readwrite state. You are not charged for merged or split shards.

For example, you want to merge three shards that are in the readwrite state. After you merge the shards, only one shard is in the readwrite state. On the day when you merge the shards, you are charged for three shards. On the next day, you are charged for one shard.

Note By default, two shards are created when you create a Logstore. For more information, see Why am I charged for active shards?
  • Pay-as-you-go: Daily fee of active shards = Number of shards in the readwrite state × Price per shard.
  • Resource plan: Purchased resource plans are used to offset the fees of billable items based on the CUs of the billable items.
31 shard days per month
Notice Free quotas are provided only when you do not use resource plans to offset the fees of consumed resources.
Dedicated SQL The fee is calculated based on the CPU time that is consumed when you perform query and analysis operations. Unit: core hour. The unit indicates the fee of one core that is used for 1 hour. For more information, see Billing example of Dedicated SQL.
  • Pay-as-you-go: Daily fee of Dedicated SQL = CPU time that is calculated by hour × Price per hour.
  • Resource plan: Purchased resource plans are used to offset the fees of billable items based on the CUs of the billable items.
None