How do you troubleshoot inconsistent cost attribution in Cloud Cost Management?

Start by checking the completeness of the underlying billing export itself - confirm the cloud provider's cost and usage report (or equivalent) is generating complete files without gaps, since a partial or delayed export will show as a genuine drop in attributed cost that has nothing to do with Datadog's tagging logic at all.

Check for a timing mismatch: cloud providers typically finalize detailed billing data with some lag, so cost figures for the most recent day or two may look artificially low or incomplete simply because the underlying data hasn't fully landed yet, not because attribution logic is actually wrong.

Audit tagging consistency on the resources themselves - inconsistent or missing tags (a resource tagged Team in one place and team elsewhere, or simply untagged) will cause that resource's cost to fall into an unallocated bucket rather than the team it should logically belong to, and this is the single most common root cause of attribution looking 'wrong.'

For shared or pooled resources (like a shared Kubernetes cluster running workloads for multiple teams), check how the allocation rule for that shared cost is actually configured - an unexpected default allocation method (evenly split versus usage-proportional, for instance) can look like a data error when it's actually a configuration choice about how shared cost should be divided.

Finally, cross-check a specific discrepancy against the raw cloud provider billing console directly for the same resource and time window, to isolate whether the mismatch originates in the cloud provider's own billing data or in Datadog's processing/attribution of it - that distinction determines whether the fix belongs in cloud tagging hygiene or in the Cloud Cost Management configuration itself.