Announcement
Resource Labels and Tags in Cost Anomaly Details
By Nikola Keskinov
·Shipped by
Route anomalies to the right team, faster
When a cost anomaly fires, the first question is often "whose problem is this?" In many cases, answering that means leaving the anomaly, looking up the affected resources, and cross-referencing their tags or labels to identify an owner.
Cost anomaly details now surface the user-defined tags (or labels in Google Cloud) attached to each resource contributing to an anomaly in the anomaly detail view, Slack notifications, and via the Anomalies API.
Tags and Labels are ordered by cost impact, so the most relevant owners and cost centers appear first. This works with your existing tagging strategy, so no additional configuration is needed. If your resources carry team, env, cost-center, or any other user-defined tags, those will show up automatically.
To learn more, check out our Help docs or raise a support ticket to speak to a DoiT expert.
