Investigate anomalies
DoiT Cloud Navigator: All tiersThe DoiT console provides multiple ways to help you understand cost anomalies.
Required permissions
- Attributions Manager, Anomalies Viewer, Cloud Analytics
View a cost anomaly
To view a specific cost anomaly:
Log in to the DoiT console, select Governance from the top navigation bar, and then select Cost anomalies.
On the Cost anomalies page, find the anomaly you want to see the details of.
Select View at the rightmost end of the anomaly entry. You'll see a cost anomaly chart and a list of resources that caused the anomaly.
The anomaly properties displayed on the Cost anomalies list page are shown above the anomaly chart with the following additional fields:
Billing account ID: For Google Cloud it is the Cloud Billing account ID that the usage is associated with. For AWS it is your DoiT customer ID (if you're on a Dedicated payer account) or your CloudHealth account ID (if you're on a Consolidated billing account). For Azure it is the unique identifier of your Azure subscription; you can also find the Subscription ID on the DoiT console's Assets page.
Attribution: The group of resources being monitored. By default, the anomaly detection service monitors three preset attributions:
All AWS Resources,All GCP Resources, andAll Azure Resources. You can also Monitor cost anomalies on other specific subsets of your overall cloud spend.
Acknowledge a cost anomaly
When you receive a cost anomaly, you can classify it as an anomaly, or a false alarm. Both when it was an anomaly and when it wasn't, you can choose the specific reason why you classify it as such. This way, you help us get better at detecting future anomalies and you help your team become faster in working through them.
To learn more about acknowledging anomalies, read how to manage anomalies according to FinOps.
To acknowledge a cost anomaly:
Log in to the DoiT console, select Governance from the top navigation bar, and then select Cost anomalies.
On the Cost anomalies page, find the anomaly you want to acknowledge, and select View at the rightmost end of the anomaly entry.
On the specific anomaly page, select Acknowledge anomaly.
Classify the anomaly with one of the options available, and add comments for your future reference.
Select Save.
After you acknowledge an anomaly, you'll see the information you entered in the Acknowledge anomaly dialog every time you view its details. Additionally, its status will get updated in the Cost anomalies page.
Cost anomaly charts
A cost anomaly chart contains the following information:
Anomaly detected: When a spike was detected as a cost anomaly.
Anomaly inactive: When the anomaly became inactive. See Dynamic updates for more information.
Cost at time of detection: Value derived from the available cost data when an anomaly was detected. This field applies only to the point of Anomaly detected.
Cost since time of detection: Value derived from the cost data received after an anomaly was detected. The anomaly detection system keeps updating this field until the anomaly becomes
Inactive.Cost adjustment since time of detection: Negative value derived from the cost data received since an anomaly was detected.
Normal range: It's depicted as a shaded area on an anomaly chart. The example below shows one point that exceeds the upper bound of the normal range while also meeting the other criteria. It is reported as an anomaly.
Cost of anomaly: The difference between the actual total cost and the maximum cost in the normal range calculated at that moment. Moving your mouse over the bar that indicates Anomaly detected will show the relevant numbers.
Contributory resources
A list of Resources contributing to this anomaly is displayed below the cost anomaly chart. Combining with Anomaly details, this list helps you better understand what caused the anomaly and allows you to make informed decisions swiftly.
Check anomaly details
Anomaly details are available only for anomalies detected after May 25, 2023.
To gain a quick understanding of an anomaly, select Anomaly details in the upper-right corner of the cost anomaly chart.
The anomaly details consist of three parts:
Summary: a brief on the anomaly, including the rationale and the main contributors to the spike
SKU explanation: a breakdown of top SKUs that drove the cost increase
Optimization: a list of suggestions on how you can optimize the costs associated with the specific service
Open in reports
To decide whether a detected anomaly is really an issue in the context of your business, select Open in Report in the upper-right corner of the cost anomaly chart. It will open a cloud analytics report that groups costs by SKUs and uses anomaly properties (billing account, scope, service, attribution) as filters.
Cloud analytics reports always use the latest usage and cost data available, while the data in cost anomaly charts is only updated until the anomaly becomes Inactive.
