Skip to main content

Cost anomalies

Cloud cost anomaly detection offers end-to-end monitoring of spikes in your Google Cloud or Amazon Web Services billing across all your projects and services.


DoiT cost anomaly detection service leverages our machine learning algorithm. It monitors billing data and analyzes the trend of spending in your environment. In addition, the machine learning model identifies billing patterns across customers, forecasts your cloud spending, and constantly improves itself to provide even more accurate results.

Billing records that don't align with your anticipated spending behavior are identified for its deviation from the established patterns. You can also get insights into which resources are causing the anomalies and take corrective actions. The anomaly detection engine is always running. You can also choose email notifications for near-real-time email alerts on detected anomalies.


Required Permissions: Users Manager

Manage anomaly notifications

To manage your anomaly notifications:

  1. Log in to the CMP.

  2. Select your account name in the upper-right corner of the top navigation menu, and then select your name from the drop-down menu.

  3. On your Users page, select Notifications from the left-hand menu.

  4. To be notified of potential anomalies, select the Cloud Cost Anomalies checkbox, and then set the minimum severity threshold you want to be alerted on.

    There are three levels of severity:

    • Information
    • Warning
    • Critical

    By default, the threshold for email alerts is set to Warning or higher (i.e., >= Warning). You can modify this setting to increase or decrease the number of alerts you receive.


The data analysis begins as soon as you sign up. However, for anomaly detection to work properly, we need to gather at least seven full days of reference data in a specific project.

In case anomaly detection is critical to your operation, we strongly recommend that you wait this seven-day period out before making any significant changes to your cloud spending.

Configure custom anomaly scopes

To monitor a specific subset of costs in your accounts, you can use attributions to define a custom scope.

For example, to create anomalies to only monitor your production infrastructure, you can create a custom attribution that defines your environment and then enable it for monitoring in Attributions Settings.

View anomalies

We store all the detected cost anomalies. To access cost anomalies:

  1. Select Governance from the top navigation menu, and then select Cost anomalies.

  2. To view a specific anomaly, select the View button at the rightmost end of the anomaly entry.


    The Cost of Anomaly is calculated as the gap between the actual cost and the maximum cost in the normal range.

On the anomaly page, you can choose to investigate further or give feedback to fine tune the alerts.

Investigate anomalies further

To zoom in on a specific anomaly and check whether it's really an anomaly in the context of your business, select the Investigate button in the top right-hand corner of the screen to launch the corresponding Cloud Analytics Report.

Fine-tune alerts with direct feedback

To reduce the number of false alerts, you can provide a thumbs-up or a thumbs-down for each alert. We use this information to fine-tune the anomaly detection algorithm and improve the results.