We are thrilled to announce an important update to one of our most popular features - Cloud Cost Anomaly Detection.

Until recently, the DoiT Console displayed the anomalies, with a breakdown of the GCP or AWS services making the most contribution to the anomaly. While this has been helpful for general Root Cause Analysis, we understand that more granular insights can provide an even better understanding of cost anomalies and what resources are driving the costs up.

The new version shows the SKUs contributing to the cost anomaly and the Resources associated with those SKUs. This enhancement will enable you to identify the specific resources that have caused an anomaly, improving your ability to manage and control cloud costs more effectively.

For example, this is how we were displaying anomalies until today. You can clearly see an anomaly with Amazon CloudWatch USW2-DataProcessing-Bytes, but there is no information on what caused this big spike in CloudWatch usage.

However, with this release, we are also displaying the Resources contributing to the anomaly, in this case, AWS RDS PostgreSQL instance prod-db-us-west-2.

We believe this update will streamline your anomaly incident management process by offering a more holistic view of cost anomalies, thereby aiding you in making informed decisions swiftly. By understanding what has led to an unexpected increase in cost, you can now drill down to the root cause and take appropriate actions more promptly.

More information about Cost Anomalies is in our Help Center.