Notifications
Clear all
Topic starter
19/08/2026 3:28 pm
TL;DR: Datadog bills usually climb because telemetry volume grows across logs, metrics, spans, and hosts faster than anyone governs the inputs, according to Sawmills, and the article maps each meter to the upstream pipeline control that can curb it. Cost control shifts from vendor pricing to telemetry governance, where sampling, filtering, tag hygiene, and retention policy determine the bill.
NHIMG editorial — based on content published by Sawmills: What actually drives your Datadog cost, and the upstream control for each meter
By the numbers:
- Splunk's State of Observability 2025 surveyed 1,855 ITOps and engineering professionals.
Questions worth separating out
Q: How should teams control Datadog cost without cutting useful telemetry?
A: Start by governing the telemetry inputs rather than the bill itself.
Q: Why do custom metrics often become the biggest observability cost?
A: Because each distinct metric-and-tag combination is billable, so high-cardinality labels multiply cost far faster than traffic alone.
Q: What breaks when logs and spans are sampled too late?
A: If sampling happens only after data has already crossed the ingestion layer, the expensive part is already paid for.
Practitioner guidance
- Map each Datadog meter to an upstream control point Create a control map for logs, custom metrics, spans, and hosts so every billing driver has a specific pipeline decision owner.
- Govern metric labels before they become billable series Define an approved label set for application metrics and remove or transform high-cardinality tags such as user_id, pod_name, and endpoint where they are not essential.
- Use value-based routing for logs and spans Route audit-grade records to long-retention searchable storage, but sample or down-tier routine debug, health-check, and success-path telemetry.
What's in the full article
Sawmills' full article covers the operational detail this post intentionally leaves for the source:
- The billing mechanics behind log ingest versus indexing, including how retention tiers change the final cost curve.
- The meter-by-meter breakdown for custom metrics, APM spans, and infrastructure hosts with concrete examples of where volume expands.
- The pipeline control examples for filtering, sampling, redaction, and routing that are needed to implement the article's cost model.
- The practical comparison of upstream telemetry control options for teams building a permanent governance process.
👉 Read Sawmills' analysis of what actually drives Datadog cost →
Datadog cost is a telemetry governance problem, not a pricing one?
Explore further
19/08/2026 4:12 pm
Telemetry governance is now a control problem, not a procurement problem. The article shows that observability cost grows from data shape, not just vendor pricing. That is a familiar pattern in identity security too: when inputs are not governed, the downstream platform inherits the blast radius. For practitioners, the lesson is to move control upstream where data is created and tagged.
A question worth separating out:
Q: How do you know if telemetry cost controls are actually working?
A: Look for lower billable volume without losing incident value. Good signals include stable error coverage, reduced high-cardinality series, fewer retained routine logs, and trace sampling that still preserves outliers. If the bill falls but troubleshooting becomes harder, the control is too blunt and needs adjustment.
👉 Read our full editorial: Datadog cost grows in telemetry pipelines, not rate cards
