Notifications
Clear all
Topic starter
19/08/2026 3:41 pm
TL;DR: Datadog bills balloon when high-cardinality tags, noisy logs, and over-indexed traces turn telemetry into a continuously expanding cost surface, according to Sawmills. The deeper issue is governance: human review loops cannot keep pace with developer- and agent-generated telemetry, so cost control has to move into the pipeline.
NHIMG editorial — based on content published by Sawmills: Datadog Cost Optimization, One Tag Can 1000x Your Bill
Questions worth separating out
Q: What breaks when high-cardinality telemetry tags are not controlled?
A: Billable timeseries expand multiplicatively, so a single metric can become thousands or millions of unique series.
Q: When should organisations move telemetry cost control into the pipeline?
A: They should do it as soon as multiple teams or agents can create instrumentation independently.
Q: What do security and platform teams get wrong about telemetry spend?
A: They often treat cost as a retention problem or a quarterly cleanup task.
Practitioner guidance
- Implement cardinality limits at ingestion Block or aggregate tags such as pod_name, request_id, user_id, and container_id before they create billable series.
- Separate sampling policy from agent defaults Define head-based and tail-based sampling rules by service criticality and error sensitivity.
- Classify log streams by query value Index only streams that are actively searched during incidents or investigations.
What's in the full article
Sawmills' full analysis covers the operational detail this post intentionally leaves for the source:
- API-based cardinality auditing workflow for ranking the most expensive metrics
- Sample Datadog filtering and sampling patterns for logs, custom metrics, and APM traces
- Pipeline-level shaping logic for reducing billable telemetry before it reaches Datadog
- Implementation guidance for teams moving from quarterly cleanup to continuous control
👉 Read Sawmills' analysis of Datadog cost governance and telemetry sprawl →
Datadog cost sprawl: what telemetry governance teams need to change?
Explore further
19/08/2026 4:20 pm
Telemetry governance debt is now a cost-control problem. The article shows that spend does not rebound because teams fail once, but because the source of cost keeps changing faster than review processes can respond. That is the same structural pattern NHIMG sees in NHI estates where lifecycle drift, not a single misconfiguration, creates persistent exposure. Practitioners should treat telemetry shaping as a governed control layer, not a cleanup task.
A question worth separating out:
Q: How should teams govern telemetry when coding agents are creating instrumentation?
A: Use policy checks for new tags, metric dimensions, and log fields before code is merged or deployed. Agents can generate plausible defaults at machine speed, so the control must shift from human review alone to automated enforcement at the pipeline boundary.
👉 Read our full editorial: Datadog cost sprawl is a telemetry governance problem, not a cleanup task
