You can purchase resource plans in advance to offset usage fees. When fees are settled, usage is first deducted from your resource plans. This topic describes the basics of resource plans.
Resource plan
Simple Log Service provides the following resource plan.
Resource plan | Description |
Resource plan | You can use this plan to offset the fees of all billable items in Simple Log Service. Note You receive a fixed resource quota each month for the duration of the plan. The quota resets at the end of each month, and any unused portion does not carry over. |
Resource plan details
You can use a resource plan to offset the fees of all billable items in Simple Log Service. Resource plans with a higher quota and a longer validity period are more cost-effective. The system calculates your daily Simple Log Service usage and deducts it from the resource plan quota. During the validity period, you receive the same resource quota each month. If the monthly quota is exhausted, subsequent usage is billed on a pay-as-you-go basis.
Both the pay-by-feature and pay-by-ingested-data billing modes are supported.
Simple Log Service offers yearly subscriptions for resource plans (one year or longer) with discounts based on the specifications. The exact discount is shown on the purchase page. The pay-as-you-go pricing remains unchanged. You can benefit from the discount policy only after you purchase a resource plan for one year or longer.
When you purchase a resource plan, Alibaba Cloud charges a one-time, upfront fee. For example, if you purchase a 1-year, 100 CU resource plan, you are charged the full annual fee on the day of purchase.
The unit for resource plan specifications is the cost unit (CU).
Resource plans support the pay-by-feature and pay-by-ingested-data billing modes.
The number of CUs from a resource plan consumed to offset a billable item is equivalent to the item's pay-as-you-go unit price. For example, the pay-as-you-go price for read/write traffic for Simple Log Service on the is USD 0.045/GB. Therefore, offsetting 1 GB of read/write traffic consumes 0.045 CUs. For more information, see the following tables:
Pay-by-feature
Billable item | Resource plan |
Read/Write traffic (per GB) | 0.045 CU |
Storage usage - Hot log storage (per GB/day) | 0.002875 CU |
Storage usage - Time series storage (per GB/day) | 0.00048 CU |
Index traffic - Log index (per GB) | 0.0875 CU |
Index traffic - Time series index (per GB) | 0.02721 CU |
Data transformation (per GB) | 0.0204 CU |
Data shipping to OSS (JSON or CSV format) (per GB) | 0.0068 CU |
Data shipping to OSS (Parquet or ORC format) (per GB) | 0.0272 CU |
Data shipping to MaxCompute (per GB) | 0.0272 CU |
Data shipping to AnalyticDB (per GB) | 0.0272 CU |
Data shipping to ApsaraDB for Lindorm (per GB) | 0.0272 CU |
Phone call notifications for alerts (per call) | 0.02041 CU |
Text message notifications for alerts (per message) | 0.0068 CU |
Dedicated SQL (per core × hour) | 0.05174 CU |
Storage usage - IA log storage (per GB/day) | 0.000762 CU |
Storage usage - Archive log storage (per GB/day) | 0.000259 CU |
Index traffic - Log index - Query type (per GB) | 0.0146 CU |
Scan traffic (per GB) | 0.00762 CU |
Read/Write operations (per million operations) | 0.03 CU |
Active shard lease (per shard/day) | 0.01 CU |
Internet read traffic (per GB) | 0.2 CU |
Pay-by-ingested-data
Billable item | Resource plan |
Raw data writes (per GB) | 0.061 CU |
Storage usage - Hot log storage (per GB/day) | 0.002875 CU |
Storage usage - IA log storage (per GB/day) | 0.000762 CU |
Storage usage - Archive log storage (per GB/day) | 0.00026 CU |
Internet read traffic (per GB) | 0.2 CU |
FAQ
Purchase resource plans
Why do I have overdue payments even if I purchase a resource plan?
What do I do if the quota of a resource plan is insufficient?
Use resource plans
How am I charged if the quota of a resource plan is exceeded?
Why is the quota of a one-year resource plan exhausted in one month?