Untagged spend reporting
Parent: Atlas Cost Commitments, Cross-Org Billing and FinOps Tooling · Published reference · snapshot 2026-10-30
↓ Facts as markdownall context files
Source-anchored research for Untagged spend reporting. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Structure and components
- For Atlas cost allocation, Vantage's August 31, 2026 comparison describes virtual tagging, while MongoDB documents native resource tags. These are distinct metadata paths; inference: an unallocated-spend report should state whether allocation came from native tags or reporting-layer rules. (medium confidence) (verified as of 2026-08-31) [source]
How it works
- Atlas invoice CSV and Admin API tags reflect the configuration when the export is generated or the API is called. A tag change within a billing cycle makes the invoice show the latest configuration. Methodological implication: retain dated extracts or a tag-history record before using these exports to compare historical untagged spend. (low confidence) (verified as of 2026-10-14) [source]
- Atlas invoice CSVs represent each resource tag key as a separate Tag/<key> column containing its value. MongoDB's release example shows blank cells when a cluster lacks the corresponding Cost-Center tag, providing a basis for missing-required-key reporting from exported line items. (high confidence) (verified as of 2026-10-14) [source]
Measurements and reference values
- A published AWS sandbox investigation combines cost rows with CloudTrail creation evidence to distinguish tags omitted at provisioning from tags removed later. Its advertised 17% allocation gap is modeled scenario spend, not an observed production loss; the repository explicitly separates those evidence types. (low confidence) [source]
Problems, failure modes and limitations
- Atlas treats tag keys and values as case sensitive, so environment and Environment are different keys. Its tagging guidance recommends consistent formats; independent audit tooling detects key and value drift. Inference: validate canonical keys and values before interpreting missing-tag cost as a provisioning failure. (high confidence) [source]
Comparisons and alternatives
- Missing-tag checks should follow an explicit policy for required keys and acceptable values. FinOps guidance requires meaningful valid values, rather than mere nonempty fields, and consistent scope and time period when comparing compliant cost with total cost. Policy-compliant cost and cost with any arbitrary tag are different measures. (low confidence) [source]
Facts and statements
- Atlas invoice CSVs expose resource tags as Tag/<key> columns, and the billing API exposes line-item tags. These are documented inputs for reporting spend by team, environment, or cost center. (high confidence) (verified as of 2026-10-14) [source]
- MongoDB's billing-tag announcement, updated March 11, 2025, says a missing cluster tag produces blank invoice cells, tags typically appear within 48 hours, and non-cluster-level charges are ineligible for tagging at that time. This is dated guidance, not proof of every service's current eligibility. (low confidence) (verified as of 2025-03-11) [source]
- The FinOps Foundation publishes untagged resource cost divided by total resource cost, multiplied by 100, and also permits restricting both numerator and denominator to taggable resources. A report should identify which denominator it uses; the independent Untagged auditor explicitly adopts the taggable-cost variant. (high confidence) [source]
- Having any tag does not establish compliance with all required allocation tags. The Foundation's playbook explicitly limits its KPI in this way, while the Untagged auditor checks the complete selected policy and rejects placeholder values. Inference: report required-key completeness separately from basic tag presence. (high confidence) [source]
- Report spend-weighted allocation coverage separately from the fraction of compliant resources. The Untagged auditor maintains separate measures, and the Foundation's KPI repository distinguishes resource-tag coverage from the share of spend that is untaggable; one aggregate score would conceal these differences. (high confidence) [source]
- Vantage's February 2023 Atlas integration announcement describes ingesting invoice line items and grouping MongoDB costs by service, cluster, and tag. Together with Atlas's documented API tags, this demonstrates a third-party reporting path; the announcement does not establish an Atlas-specific automatic untagged-spend remediation feature. (medium confidence) [source]
- The FinOps Foundation playbook measures compliant-resource cost divided by total resource cost, multiplied by 100. It also permits a denominator limited to taggable-resource cost. Therefore, an untagged-spend report must disclose its denominator and treatment of untaggable charges; these variants are not directly comparable. (low confidence) [source]
- MongoDB recommends standard tag naming, mandatory-tag governance, and regular checks for missing or improper tags. Atlas treats keys and values as case sensitive, so environment and Environment are distinct keys; a reporting policy must handle such spelling and case differences explicitly. (high confidence) (verified as of 2026-10-14) [source]
- Vantage's February 1, 2023 Atlas launch documentation describes read-only Invoices API ingestion, combined Atlas and infrastructure-provider reporting, and grouping MongoDB costs by service, cluster, and tag. This establishes a reporting integration, but does not by itself establish an explicit missing-tag filter or a policy-compliant untagged-spend KPI. (low confidence) (verified as of 2023-02-01) [source]
Children
- Required-tag completeness versus any-tag coverage (frontier)
- Taggable-spend denominator selection (frontier)
- Historical tag snapshots for allocation audits (frontier)
Frontier under this node: Historical tag snapshots for allocation audits, Required-tag completeness versus any-tag coverage, Taggable-spend denominator selection