> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Reduce Datadog APM Span Overage

> Cut Datadog APM span overage by lowering ingestion sampling and tightening retention filters.

Datadog APM plans include an allotment of ingested and indexed spans. Anything above it is billed as overage, at on-demand rates. nOps finds organizations paying on-demand span overage every day and estimates the saving from staying inside the allotment.

| | |
| - | - |
| **Cloud** | Datadog |
| **Category** | Observability |
| **Service** | Datadog APM |
| **Action** | Modify |
| **Effort** | Medium |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 14 days |
| **Source** | nOps |

## 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

1. In Datadog, open **APM → Ingestion Control** and find the services that ingest the most spans.
2. Lower the ingestion sampling rate for noisy, low-value services (in the Datadog Agent or tracing library configuration, or remotely from Ingestion Control).
3. In **APM → Retention Filters**, narrow custom filters so fewer spans are indexed.
4. 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.

## Related

* [Commit Steady Datadog On-Demand Usage](https://help.nops.io/inform/supported-recommendations/commit-steady-datadog-on-demand-usage)
* [Reduce Datadog Container Overage](https://help.nops.io/inform/supported-recommendations/reduce-datadog-container-overage)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.