Why it matters
Span volume grows with traffic and new services, and default sampling often keeps far more spans than anyone looks at.How nOps finds it
nOps reads the last 14 complete days of Datadog billing for each organization and product. An organization is flagged when it paid on-demand ingested-span or indexed-span charges on all 14 days. Included allotments are never billed, so every billed line is overage. The saving is the lowest daily on-demand charge times 30, which is the overage that was always there, and must be at least $5 a month. Overage already prepaid in your commitment is not counted.Before you start
Datadog admin access to APM ingestion and retention settings, and agreement from service owners on what to sample.How to implement
- In Datadog, open APM → Ingestion Control and find the services that ingest the most spans.
- Lower the ingestion sampling rate for noisy, low-value services (in the Datadog Agent or tracing library configuration, or remotely from Ingestion Control).
- In APM → Retention Filters, narrow custom filters so fewer spans are indexed.
- Check Plan & Usage over the next weeks to confirm span usage is back inside the allotment.
Risks and considerations
- Lower sampling means fewer traces to investigate. Keep error and slow traces, which Datadog can keep regardless of sampling.
- How far volume can be cut is your call, so the saving is an upper bound.
- To roll back, restore the previous sampling rates and filters.