Skip to main content

Why does the Explore Traces graph show a greater count of spans than expected?

Issue

I noticed that the count of spans in the Explore Traces graph looks inflated compared to the number of sampled spans shown. Where are these spans coming from?

Applies To

  • Users report spans and using the Explorer Trace view

Resolution

Explore Traces uses extrapolation based on the sample rate applied to your spans. The same is showing in the UI:

Screenshot 2025-09-05 at 12.49.15 PM.png


This means if your spans are sampled at 10% (0.1) and 10 spans are generated, only 1 span will be ingested and shown under Span Samples, but the graph in Explore Traces will show 10, extrapolated to represent the full 100% sample count.

Screenshot 2025-09-05 at 1.09.34 PM.png


If you’d like to see the ingested number of spans without extrapolation, use the Stats page.

Did this answer your question?