View and manage cost anomalies

Anomaly detection helps you manage unexpected costs across your billing account's projects. These anomalies are spikes or deviations in usage costs that differ from your expected spend, when compared to historical spending patterns. Usage costs are calculated using list prices and any contracted or negotiated pricing that's available for your Cloud Billing account. Cost totals are gross costs and exclude committed use discounts and other credits.

The Anomalies dashboard displays all cost anomalies associated with your projects, within the linked billing account. You can use the Anomalies dashboard to do the following:

  • Investigate the root causes of anomalies.
  • Customize your view by setting a cost impact threshold amount.
  • Set up automated alerts and notifications for detected anomalies.
  • Provide feedback on detected anomalies to improve the tool's accuracy.

Anomalies can only be detected for projects with at least six months of historical spend.

For reseller accounts and subaccounts, this feature is only available if you enable project-based cost visibility. Resellers can only view anomalies for their projects. To view anomalies for a subaccount, you must switch to the subaccount. To enable project-based cost visibility, contact Cloud Billing Support.

Permissions required for this task

You can view and manage anomalies for all projects on a Cloud Billing account or for individual projects. To manage anomalies for all projects on a Cloud Billing account, you need permissions on the billing account. To view anomalies for a specific project, you need billing-specific permissions on the project.

Users with Cloud Billing account permissions Users with project-level permissions only

To gain the necessary permissions using a predefined role, ask your administrator to grant you one of the following predefined Cloud Billing IAM roles on your Cloud Billing account:

To set up Pub/Sub notifications for anomalies, you need additional permissions. To gain the necessary permissions using a predefined role, ask your administrator to grant you the following role on the target project that contains the Pub/Sub topics:

To gain the necessary permissions using predefined roles, ask your administrator to grant you one of the following predefined Cloud Billing IAM roles on the project:

Access the Anomalies dashboard

To access the Anomalies dashboard, complete the following steps for your access level:

Users with Cloud Billing account permissions Users with project-level permissions only
  1. In the Google Cloud console, go to your Cloud Billing account.

    Go to your Cloud Billing account
  2. At the prompt, select the Cloud Billing account that you want to view anomalies for.

    The Billing Overview page opens for the selected billing account.

  3. In the Cost management section of the Billing navigation menu, select Anomalies.
  1. Sign in to the Google Cloud console.

    Open Google Cloud console
  2. Select the project that you want to view anomalies for. This project must be one that you own.
  3. Open the Google Cloud console Navigation menu and select Billing.

    If you're prompted to choose which billing account you want to view and manage, click Go to linked billing account to view the billing account that's linked to your selected project.

    The Billing Overview page opens for the selected billing account.

  4. In the Cost management section of the Billing navigation menu, select Anomalies.

Analyze root causes of anomalies

Each anomaly includes a granular Root cause analysis panel that helps pinpoint the source of the cost spike. To open the panel and view the details of an anomaly, click the anomaly date.

The Root cause analysis panel shows the top services, regions, and SKUs that contributed to the spike in spend. If the anomaly is equally spread across services, regions, or SKUs, you won't see any top contributors in the Root cause analysis panel.

Click any of the links in the Root cause analysis panel to open a Billing Report that's filtered by the project you're viewing, and also by service, region, or SKU, depending on the link you select.

In the Root cause analysis panel, you can also share feedback about the anomaly to help optimize anomaly detection.

Manage anomalies

Billing Account Administrators can set threshold and notification preferences for all anomalies. On the Anomalies page, click Manage anomalies to customize thresholds and notifications.

Set a cost impact threshold

To focus on cost anomalies that are significant to you, set a cost impact anomaly threshold. The threshold amount filters your view to show only anomalies exceeding a certain cost deviation (for example, $200). If you set up notifications, you also receive alerts when a cost anomaly crosses the threshold value.

This threshold value is in your billing account's local currency and can only contain positive numeric values, including up to two decimal places. You can't use negative or non-numeric values.

For users with billing-account-level access, the threshold amount automatically sets a Cost impact filter on the anomalies list, showing only anomalies that cross the cost impact threshold. You can remove the Cost impact filter to see all anomalies, but the filter is reapplied the next time you visit the page.

Users with project-level access can view all detected anomalies for their project. For project-level users, the Cost impact filter isn't automatically set on the anomalies list, but you can manually set filters in the Anomalies dashboard.

Set up notifications

On the Manage anomalies page, you can set how you want to be notified about anomalies that go above your cost impact threshold. You can configure email or Pub/Sub notifications.

You can change your notification settings at any time. Notification configurations apply to all projects on your billing account. You can't set up notifications for a subset of projects.

Set up email notifications

To set up email notifications, complete the following steps:

  1. From the Anomalies dashboard, click Manage anomalies.
  2. If you haven't already, enter an Anomaly threshold value for Cost impact. This amount is the threshold value that triggers notifications.
  3. In the Email notifications section, set the email recipients (Billing admins, Essential contacts, or Project owners) and the frequency of emails for each recipient (every Individual anomaly or a Daily summary).

    • For Essential contacts, selecting Individual anomaly sends notifications to the designated Essential Contacts, in the Billing category, for the project.
    • For Essential contacts, selecting Daily summary sends notifications to the designated Essential Contacts, in the Billing category, for the organization.
    • Project owners can receive notifications only for individual anomalies on projects that they own.
  4. Click Save.

Set up Pub/Sub notifications

To set up Pub/Sub notifications for anomalies, complete the steps in Set up programmatic notifications.

Optimize anomaly detection

The AI-powered anomaly detection algorithm constantly learns and improves, but your feedback helps it adapt faster to your business needs. To provide feedback, complete the following steps:

  1. In the list of anomalies, click the date of an anomaly to open its Root cause analysis panel.
  2. For Is this an anomaly?, select one of the following options:
    1. Yes, it's an unexpected cost increase: Select this option if the anomaly is unexpected and an unintended cost increase.
    2. Yes, but it's an expected cost increase: Select this option if the anomaly is an expected cost increase to meet your business needs. To help Google's anomaly detection models adapt, you can provide more context around the specific business reason for the anomaly (for example, if you have active migrations underway, are using new Google Cloud resources, or if the cost increase is temporary).
    3. No, the cost impact is insignificant: Select this option if the anomaly has a cost impact that you don't consider to be significant.
  3. Click Submit feedback.

After you submit your feedback, it's recorded with a timestamp.

To change previously submitted feedback, complete the following steps:

  1. Open the Root cause analysis panel.
  2. Change your selection using the provided options.
  3. Click Submit feedback.