Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
6 changes: 4 additions & 2 deletions docs/product/explore/trace-explorer/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -185,7 +185,7 @@ Similarly, Sentry incorporates the weight into **sum**:

Trace Explorer will display **Sum: 1.4ms**.

### Averages and percentiles
### Averages and Percentiles

Averages and percentiles are **weighted**. You don't just average the 2 spans -- Sentry accounts for the fact that they represent a larger dataset. For example, the weighted average works like this:

Expand All @@ -199,7 +199,9 @@ Sentry treats this as a representation of the average across all 12 estimated sp

If your sampling rate is **too low** for an accurate extrapolation (for example, keeping less than 5% of an already low number of spans), Sentry may show a **low sampling rate warning**. This lets you know that extrapolation might be less reliable, especially for more restrictive queries.

![Trace Explorer Screenshot](./img/Trace_explorer_low_samples.png)
<div style={{width: '450px'}}>
![Trace Explorer Warning](./img/Trace_explorer_low_samples.png)
</div>

Even if you sample your spans, **Trace Explorer's extrapolation gives you reasonably accurate answers** for counts, averages, and percentiles -- without you needing to do anything extra.

Expand Down
Loading