Anomaly Detection Policy Not Triggering

Products

• CloudHealth

Issue/Introduction

The Anomaly Detection policy did not trigger an alert, even though there was a significant cost increase or decrease for a specific service

Resolution

The Anomaly Detection policy may not trigger an alert if the cost change does not meet the threshold defined in the policy condition, even when overall service costs appear to have increased or decreased significantly. Keep in mind that the policy evaluates each anomaly individually (not aggregated anomalies per service), and anomalies are detected based on a combination of service, account, and region.