Application Monitoring Pro Edition charges by Agent × Hour -- the number of monitoring agents multiplied by the hours they run. A single instance running 24/7 for 30 days (~720 Agent × Hours) costs approximately USD 29.81 in the Chinese mainland or USD 41.76 in other regions.
The prices in this topic are for reference only. Actual prices on the buy page prevail.
Billing unit
The billing unit is Agent × Hour. One agent monitors one application instance, such as a Tomcat instance or a Java process.
Metric | Value |
|---|---|
1 instance running 24 hours | 24 Agent × Hours |
1 instance running 24/7 for 30 days | ~720 Agent × Hours |
Default trace data retention | 30 days |
Default metric data retention | 90 days |
Pricing
Specification | Regions in the Chinese mainland | China (Hong Kong) Region | Regions outside China (such as Singapore and US (Silicon Valley)) |
Agent × Hour | USD 0.0414 | USD 0.0580 | USD 0.0580 |
Cost estimates
The following examples show how Agent × Hour pricing translates to monthly costs.
Example 1: Single instance, 24/7
Item | Calculation | Result |
|---|---|---|
Agent × Hours per day | 1 instance × 24 hours | 24 |
Agent × Hours per month | 24 × 30 days | 720 |
Monthly cost (Chinese mainland) | 720 × USD 0.0414 | USD 29.81 |
Monthly cost (other regions) | 720 × USD 0.0580 | USD 41.76 |
Example 2: Five instances, 24/7, Chinese mainland
Item | Calculation | Result |
|---|---|---|
Agent × Hours per day | 5 instances × 24 hours | 120 |
Agent × Hours per month | 120 × 30 days | 3,600 |
Monthly cost | 3,600 × USD 0.0414 | USD 149.04 |
Example 3: Three instances, 12 hours/day (business hours), Chinese mainland
Item | Calculation | Result |
|---|---|---|
Agent × Hours per day | 3 instances × 12 hours | 36 |
Agent × Hours per month | 36 × 30 days | 1,080 |
Monthly cost | 1,080 × USD 0.0414 | USD 44.71 |
Billing cycle
The ARMS billing cycle is one day. ARMS calculates the resource consumption of the previous day, starting at 00:00 on the current day. Bills are typically generated before 08:00 on the settlement day. After a bill is generated, the system automatically deducts the amount from your account balance if the balance is sufficient. You can view your bills on the Expenses and Costs page and check your resource consumption in the ARMS console. For more information, see Resource usage and bills.
Bill generation may be delayed. The actual time a bill is generated may vary.
ACK cluster discount
Applications deployed in Container Service for Kubernetes (ACK) clusters receive a 50% discount on Application Monitoring Pro Edition pricing. This discount has been in effect since February 10, 2020. Changes to this discount will be communicated in advance. For more information, see Estimate preferential prices.
Included features
For a feature comparison across editions, see Edition comparison.
Application Monitoring Pro Edition allocates a daily data reporting quota of 0.7 GB per Agent × Hour, calculated at the Alibaba Cloud account level.
Daily usage | Quota calculation | Daily quota |
|---|---|---|
1 instance × 24 hours = 24 Agent × Hours | 24 × 0.7 GB | 16.8 GB |
5 instances × 24 hours = 120 Agent × Hours | 120 × 0.7 GB | 84 GB |
For more information about the policy for exceeding this quota, see [Billing Change] Notice on Policy Change for Data Exceeding the Reporting Limit in ARMS Application Monitoring Pro Edition.
Activate Application Monitoring Pro Edition
Activate the Pro Edition in the ARMS console.
FAQ
What counts as an agent?
One agent monitors one application instance -- a single Java process, Tomcat instance, or similar runtime. If an application scales to five instances, that counts as five agents.
How is the data reporting quota calculated?
The quota is 0.7 GB per Agent × Hour, aggregated at the Alibaba Cloud account level. For example, an account with 24 Agent × Hours of daily usage has a combined daily quota of 16.8 GB (24 × 0.7 GB).