You are separately charged for the billable items of Simple Log Service. For example, if you collect and store logs, you are charged a write traffic fee and a log storage fee. This topic describes the billable items of pay-by-feature and the fee calculation for each item.
You can use the pay-by-feature billing mode when you collect log data and metric data. The pricing of stored data and indexes for metric data is different from the pricing of stored data and indexes for log data. However, the pricing of other billable items for metric 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 Simple Log Service console: write traffic, read traffic, number of read and write operations, transformation traffic, shipping traffic, and storage usage.
The data is updated on a daily basis.
When you use Simple Log Service to collect data, the data is automatically compressed. The compression ratio ranges from 10:1 to 5:1.
The following table describes the billable items of pay-by-feature. For more information about pricing, visit Pricing of Simple Log Service.
Billable item | Description | Fee calculation | Free quota |
Storage usage of the hot storage tier | The storage usage 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 Simple 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 usage of the hot storage tier is calculated by using the following formula: 0.2 GB + 0.5 GB = 0.7 GB. |
| 500 MB per month Important Free quotas are provided only if you do not use resource plans to offset the fees of consumed resources. |
Storage usage of the IA storage tier | After you enable the intelligent tiered storage feature for a Logstore, you can configure the Hot Data Retention Period parameter. If the retention period of hot data exceeds the specified threshold, the data is transferred to the Infrequent Access (IA) storage tier (original cold storage tier). Then, you are charged based on the storage usage of the IA storage tier. The storage usage of the IA storage tier 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 Simple 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 usage of the IA storage tier is calculated by using the following formula: 0.2 GB + 0.5 GB = 0.7 GB. |
| None |
Storage usage of metric data | The storage usage is the total size of compressed metric data and indexes that are created on raw metric data. For example, the size of raw metric data that is uploaded to Simple Log Service is 1 GB, and indexes are automatically created. The size of indexes is 1 GB. The compression ratio is 5:1. In this example, the storage usage of metric data is calculated by using the following formula: 0.2 GB + 1 GB = 1.2 GB. |
| None |
Read and write traffic | Read and write traffic includes write traffic and read traffic.
Note When you use the consumption preview feature in the Simple Log Service console, a small amount of read traffic is generated. |
| 500 MB per month Important Free quotas are provided only if 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.
Note
|
| 500 MB per month Important Free quotas are provided only if you do not use resource plans to offset the fees of consumed resources. |
Log index traffic of Query Logstores | 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.
Note
|
| None |
Index traffic of metric data | The index traffic is calculated based on the indexes that are created on raw metric data. Indexes are created for fields. The index traffic is based on the lengths of indexed fields and field values. When you upload metric data, Simple Log Service automatically creates indexes on the metric data. For example, 1 GB of raw metric data is written to Simple Log Service. In this example, the index traffic is 1 GB. |
| None |
Read traffic over the Internet | If data is pulled over a public Simple Log Service endpoint, read traffic over the Internet is generated. The traffic is calculated based on the size of data after compression. |
| None |
Scan traffic | The scan traffic is calculated based on the size before compression. |
| None |
Data transformation | You are charged for the transformed data based on the size before compression. If data is transformed across regions, you are charged for read traffic over the Internet. The traffic is calculated based on the size of data after compression. |
| None |
Data shipping | You are charged for the shipped data based on the size before compression. You can ship data to Object Storage Service (OSS), MaxCompute, and AnalyticDB for MySQL. Note When you ship data to AnalyticDB for MySQL, 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. |
| None |
Read and write operations |
Note The number of read and write operations includes both successful and failed operations. |
| 1 million per month Important Free quotas are provided only if 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
|
| 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. |
| 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
|
| 31 shard days per month Important Free quotas are provided only if 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. |
| None |