Skip to content

Ingestion control sampling rate note #34495

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
yuandesu wants to merge 4 commits into
base: master
Choose a base branch
from
+2 −0
Open

Ingestion control sampling rate note #34495

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ea20f0e
Add note on Effective Sampling Rate estimation on short timeframes
yuandesu Feb 10, 2026
feac745
edit writting style
yuandesu Feb 10, 2026
64bd537
Update content/en/tracing/trace_pipeline/ingestion_controls.md
yuandesu Feb 11, 2026
eebd38e
Merge branch 'master' into yuandesu/ingestion-control-sampling-rate-note
yuandesu Feb 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions content/en/tracing/trace_pipeline/ingestion_controls.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,6 +110,8 @@

**Note**: If the service is not making sampling decisions, the service's resources will be collapsed under the `Resources not making sampling decisions` row.

**Note**: On short time frames (such as 1 hour or 4 hours), the Effective Sampling Rate may display below `100%` even when set to `100%`, because the calculation estimates total traces. This does not mean traces are missing or that the actual rate is below 100%.

Check notice on line 113 in content/en/tracing/trace_pipeline/ingestion_controls.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.sentencelength 

Suggestion: Try to keep your sentence length to 25 words or fewer.

#### Ingestion Reasons and sampling decision makers

Explore the **Ingestion reasons breakdown** to see which mechanisms are responsible for your service ingestion. Each ingestion reason relates to one specific [ingestion mechanism][11]. After changing your service ingestion configuration, you can observe the increase or decrease of ingested bytes and spans in this timeseries graph based on the past hour of ingested data.
Expand Down