Updated on 2025-05-28 GMT+08:00

Detection Rules

  • Cost Anomaly Detection does not monitor monthly-settled cloud services like monthly-settled CDN services billed by 95th percentile bandwidth. This function will monitor your net original costs (actual payments).
  • For more information about forecasting, see Forecasting.

Anomaly Cost Detection identifies anomalies in your pay-per-use and yearly/monthly costs.

  • Detection rules for pay-per-use costs: AI algorithms are used to identify cost anomalies. If the actual cost is greater than the maximum forecasted cost and the difference is greater than $1 USD, a cost anomaly will be recorded. Percentage of pay-per-use costs that are impacted = (Actual cost – Maximum forecasted cost)/Maximum forecasted cost

    Example: If the actual cost on July 23 is $105 USD but the maximum forecasted cost is $100 USD, a cost anomaly will be recorded in the afternoon of July 24 because the actual cost exceeds the maximum forecasted cost.

  • Detection rules for yearly/monthly cost: If the MoM growth rate of MTD costs is greater than the threshold (20% by default) you specified and the difference is greater than $1 USD, a cost anomaly will be recorded. MoM growth rate=(Cost of the current month - Cost of the same period in the previous month)/Cost of the same period in the previous month

    Example: If the actual cost from June 1 to June 23 is $100 USD and from July 1 to July 23 is $121 USD, the growth rate is 21%, which exceeds the preset threshold (20%). In this case, a cost anomaly will be recorded in the afternoon of July 24.

Delay of Cost Anomalies

Cost anomalies are not detected in real time. It may take up to a full day for the latest identified anomalies to appear. For example, if a cost anomaly occurs today and meets the detection rules, it will be recorded by the afternoon of tomorrow. If you have a specific budget and want to be notified as soon as possible, you are advised to use budget management.