Why doesn't my policy alert for an Inactive Anomaly?

Products

• CloudHealth

Issue/Introduction

Anomalies detected by Governance -> Anomaly Detection will fall into one of two statuses:

• Active - An anomaly that is ongoing.  For example, a Spike in Costs that hasn't yet been corrected.  Normally found for current billing month across the most recent billing days in that month.
  
  
• Inactive - An anomaly that is no longer ongoing and has been corrected.  Normally found for past billing data.

Anomalies transition from Active to Inactive once the root cause for the anomaly has been addressed.  For example, an increase of costs for X service on 1/1/23 - $1000 to 2/1/23 - $3000, and then a dropp back down to $1000 on 3/1/23.

Inactive Anomalies will not be considered by Policy Conditions based on the AWS Anomaly Object in policies unless the Condition makes use of the "any" option for anomalies marked below.