Billable items of pay-by-feature

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.

Precautions

You can use the pay-by-feature billing mode when you collect logs and metrics. The pricing of storage and indexes for metrics is different from the pricing of storage and indexes for logs. However, the pricing of other billable items for metrics is the same as the pricing of other billable items of logs. The billable items include data transformation, data shipping, read and write traffic, and the number of requests.
You can log on to the Simple Log Service console to view the statistics of the previous day, including the write traffic, read traffic, number of read and write operations, transformation traffic, shipping traffic, and storage usage.
Simple Log Service updates the statistics on a daily basis.
If you use Simple Log Service to collect logs, the logs are automatically compressed. The compression ratio ranges from 10:1 to 5:1.

Introduction to OCUs

Observability Capacity Units (OCUs) are a new billing unit that is provided by Alibaba Cloud Cloud Native Observability Platform. The number of OCUs is automatically calculated based on the resource usage per hour.

Alibaba Cloud plans to gradually implement metered billing on the compute-intensive capabilities of Simple Log Service. The billing unit is OCUs, which measure the actual usage of computing resources. An OCU can be used to offset the fee of 0.5 CPU cores, 2 GB of memory, or 3,000 IOPS. During fee calculation, the system calculates the numbers of OCUs based on the number of consumed cores, size of consumed memory, and IOPS consumption. Then, the system uses the largest number for billing.

For example, a compute job consumes 1 core, 2 GB of memory, and 3,000 IOPS. In this example, 2 OCUs are consumed. In a billing cycle of 1 hour, approximately 1/3 OCUs are consumed when an ingest processor processes 1 GB of data. Approximately 1/3 OCUs are consumed when the new version of data transformation processes 1 GB of data. Approximately 0.3 OCUs are consumed when rule-based data consumption processes 1 GB of data.

The following table describes the billable items of pay-by-feature. For more information, visit Pricing of Simple Log Service.

Billable item	Description	Fee calculation	Free quota

Billable item	Description	Fee calculation	Free quota
Storage usage of the hot storage tier	The fee is calculated based on the storage usage of log data in 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.	Pay-as-you-go: Daily fee of the storage usage of the hot storage tier = Storage usage per day in GB × 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 Important Free quotas are provided only when 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, logs are moved from the hot storage tier to the Infrequent Access (IA) storage tier (formerly the cold storage tier) after the specified data retention period for the hot storage tier ends. In this case, you are charged based on the storage usage of the IA storage tier. The fee is calculated based on the storage usage of log data in the IA 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 IA storage tier 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 usage of the IA storage tier = Storage usage per day in GB × 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 usage of the Archive storage tier	After you enable the intelligent tiered storage feature, logs are moved from the hot storage tier or IA storage tier to the Archive storage tier after the specified data retention period for the hot storage tier or data retention period for the IA storage tier ends. In this case, you are charged based on the storage usage of the Archive storage tier. The fee is calculated based on the storage usage of log data in the Archive 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 Archive storage tier 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 usage of the Archive storage tier = Storage usage per day in GB × 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 usage of time series data	The fee is calculated based on the storage usage of time series data. The storage usage is the total size of compressed 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 Simple Log Service is 1 GB, and indexes are automatically created. The size of the indexes is 1 GB. The compression ratio is 5:1 when the raw time series data is uploaded. In this example, the storage usage of time series data is calculated by using the following formula: 0.2 GB + 1 GB = 1.2 GB.	Pay-as-you-go: Daily fee of the storage usage of time series data = Storage usage per day in GB × 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: The fee is calculated based on the size of compressed data that is uploaded to Simple Log Service. For example, the size of raw data that is uploaded to Simple Log Service is 10 GB, and the compression ratio is 5:1. In this example, the write traffic is 2 GB. Read traffic: The fee is calculated based on the size of compressed data that is shipped to AnalyticDB for MySQL or consumed. For example, the size of raw data that is uploaded to Simple Log Service is 10 GB and then the uploaded data is shipped to AnalyticDB for MySQL, and the compression ratio is 5:1. In this example, the write traffic is 2 GB when the raw data is uploaded to Simple Log Service, and the read traffic is 2 GB when the uploaded data is shipped to AnalyticDB for MySQL. Note When you use the consumption preview feature in the Simple 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 in GB + Read traffic per day in GB) × 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 Important 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 size of indexes that are created or recreated for raw log data. Indexes are created for fields. The index traffic is based on the lengths of indexed fields and field values. For example, the size of raw log data that is written to Simple Log Service is 1 GB, and the full-text indexing feature is enabled. In this example, the index traffic is 1 GB. For example, the size of raw log data that is written to Simple Log Service is 1 GB. Indexes are created for two fields and the size of the indexes is 0.5 GB. In this example, the index traffic is 0.5 GB. Important Indexes are used to accelerate data query and analysis. To query and analyze logs, you must create indexes. For more information, see Create indexes. In other scenarios such as Simple Log Service-based data migration and data transfer, you do not need to create indexes. This billable item applies to Standard Logstores. By default, the indexing feature is disabled. If you enable the feature, index traffic is generated and storage is used by indexes. You are charged for the index traffic only once when you write data. If you create both full-text indexes and field indexes, you are charged only once for the index traffic. Simple 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 in GB × 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 Important Free quotas are provided only when you do not use resource plans to offset the fees of consumed resources.
Index traffic of log data in Query Logstores	The index traffic is calculated based on the size of indexes that are created or recreated for raw log data. Indexes are created for fields. The index traffic is based on the lengths of indexed fields and field values. For example, the size of raw log data that is written to Simple Log Service is 1 GB, and the full-text indexing feature is enabled. In this example, the index traffic is 1 GB. For example, the size of raw log data that is written to Simple Log Service is 1 GB. Indexes are created for two fields and the size of the indexes is 0.5 GB. In this example, the index traffic is 0.5 GB. Important Indexes are used to accelerate data query and analysis. To query and analyze logs, you must create indexes. For more information, see Create indexes. In other scenarios such as Simple Log Service-based data migration and data transfer, you do not need to create indexes. This billable item applies to Query Logstores. By default, the indexing feature is disabled. If you enable the feature, index traffic is generated and storage is used by indexes. You are charged for the index traffic only once when you write data. If you create both full-text indexes and field indexes, you are charged only once for the index traffic. Simple 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 in GB × 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
Index traffic of time series data	The index traffic is calculated based on the size of 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, Simple Log Service automatically creates indexes on the time series data. For example, the size of raw time series data that is written to Simple Log Service is 1 GB. 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 in GB × 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 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.	Pay-as-you-go: Daily fee of 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
Scan traffic	The scan traffic is calculated based on the size of raw data that is scanned.	Pay-as-you-go: Daily fee of scan traffic = Scan traffic per day × Price per GB of scan traffic. 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	The fee is calculated based on the size of transformed data 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.	Pay-as-you-go: Daily fee of data transformation = Transformed data per day in GB × 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	The fee is calculated based on the size of shipped data 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, API operations are called to read data and network resources are consumed. 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 in GB × 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 Simple 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. Simple Log Service automatically minimizes the number of write operations in the backend. When data is transformed, shipped to AnalyticDB for MySQL, or consumed, Simple 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 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 Important Free quotas are provided only when you do not use resource plans to offset the fees of consumed resources.
Voice calls	The fee is calculated based on the number of times that voice call notifications are sent. Note If a voice call is not answered, Simple 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 when a voice call is not answered.	Pay-as-you-go: Daily fee of voice calls = Number of times that voice call 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	The fee is calculated based on the number of times that text message notifications are sent. Note If a text message exceeds 70 characters in length, the text message is split into two messages for sending. In this case, you are charged for only one text message.	Pay-as-you-go: Daily fee of text messages = Number of times that text message 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 that are in the read/write state. You are not charged for merged or split shards. For example, you want to merge three shards that are in the read/write state. After you merge the shards, only one shard is in the read/write 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? Due to historical reasons, the number of active shards for Logstores and the number of active shards for Metricstores are separately included in the Active shards and Shard Size fields in your bill. You can obtain the total number of shards that are used based on the values of the two fields. The issue is being fixed.	Pay-as-you-go: Fee of active shards = Number of shards in the read/write 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 Important 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 execute SQL statements to analyze data. 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: Fee of Dedicated SQL = CPU time that is calculated in 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
Rule-based consumption	The fee is calculated based on the amount of resources that are consumed during rule-based data consumption. Unit: OCUs. In a billing cycle of 1 hour, approximately 0.3 OCUs are consumed when rule-based data consumption processes 1 GB of data.	Pay-as-you-go: Fee of rule-based data consumption = Consumed OCUs × Price per OCU.	None
Data transformation (new version)	The fee is calculated based on the amount of resources that are consumed when the new version of data transformation processes data. Unit: OCUs. In a billing cycle of 1 hour, approximately 1/3 OCUs are consumed when the new version of data transformation processes 1 GB of data.	Pay-as-you-go: Fee of data transformation (new version) = Consumed OCUs × Price per OCU.	None
Transfer acceleration	The fee is calculated based on the volume of uplink and downlink traffic that is generated over the endpoint for transfer acceleration. The traffic volume is the size of actual data that is transferred by using the transfer acceleration feature. If data is compressed when you upload data to Simple Log Service, the traffic is calculated based on the size of data after compression. For more information, see Use the transfer acceleration feature.	Pay-as-you-go: Fee of transfer acceleration = Uplink and downlink traffic generated during transfer acceleration × Price per GB of traffic.	None
Ingest processor	You can use ingest processors to preprocess logs before the logs are written to a Logstore. For example, you can use ingest processors to filter data, extract fields, extend fields, and mask data. The fee is calculated based on the amount of resources that are consumed during data processing. Unit: OCUs. In a billing cycle of 1 hour, approximately 1/3 OCUs are consumed when an ingest processor processes 1 GB of data.	Pay-as-you-go: Fee of ingest processor = Consumed OCUs × Price per OCU.	None