Service-level cost anomalies now show specific accounts and SKUs

Investigate service-level cost anomalies faster with account/project and SKU breakdowns.

Service-level cost anomalies catch broad spend shifts across an entire billing account and service. We recently made them faster, so alerts arrive sooner after unusual spend appears. Earlier alerts shift the bottleneck to investigation: you now need to identify the driving accounts/projects and SKUs just as fast.

For service-level detections, the Account/Project and SKU fields showed "All," since the monitor aggregates across the full scope. Technically correct, but not much help when you're trying to narrow things down.

We've updated service-level anomalies to derive specific labels from the underlying resource data:

• Specific SKU labels: See which SKUs drove the cost change instead of a blanket "All."
• Account and project context: Identify the actual accounts or projects contributing to the anomaly, pulled directly from resource data.
• Faster investigation: Jump straight to the relevant scope without manually narrowing down contributors.

This is especially useful for AI services, which often bill separate SKUs for each token type, such as input and output tokens.

The improvement applies to all new anomaly detections starting today. To get started, open Cost Anomalies in Cloud Intelligence™.