Updated extrapolation docs for clarity and adding an image #15325
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
develop-docs/application-architecture/dynamic-sampling/extrapolation.mdx
Show resolved
Hide resolved
develop-docs/application-architecture/dynamic-sampling/extrapolation.mdx
Outdated
Show resolved
Hide resolved
develop-docs/application-architecture/dynamic-sampling/extrapolation.mdx
Outdated
Show resolved
Hide resolved
develop-docs/application-architecture/dynamic-sampling/extrapolation.mdx
Outdated
Show resolved
Hide resolved
develop-docs/application-architecture/dynamic-sampling/extrapolation.mdx
Outdated
Show resolved
Hide resolved
develop-docs/application-architecture/dynamic-sampling/extrapolation.mdx
Outdated
Show resolved
Hide resolved
|
|
||
| ### Confidence | ||
| When users filter on data that has a very low count but also a low sample rate, yielding a highly extrapolated but low-sample dataset, developers and users should be careful with the conclusions they draw from the data. The storage platform provides confidence intervals along with the extrapolated estimates for the different aggregation types to indicate when there is elevated uncertainty in the data. These types of datasets are inherently noisy and may contain misleading information. When this is discovered, the user should either be very careful with the conclusions they draw from the aggregate data or switch to non-default mode for investigation of the individual samples. | ||
| When you filter on data that has a very low count but also a low sample rate, yielding a highly extrapolated but low-sample dataset, you should be careful with the conclusions you draw from the data. The storage platform provides confidence intervals along with the extrapolated estimates for the different aggregation types to indicate when there is lower confidence in the data. These types of datasets are inherently noisy and may contain misleading information. When this is discovered, you should either be very careful with the conclusions you draw from the aggregate data or switch to sample mode to investigate the individual samples. |
There was a problem hiding this comment.
We should include this image here: https://docs.sentry.io/product/explore/trace-explorer/#sampling-warnings
There was a problem hiding this comment.
I'm feeling mixed on adding this image in. I'm wondering about its usefulness in develop-docs specifically, since these users are not directly using Sentry's UI.
added 2 commits
November 4, 2025 10:59
Bundle ReportChanges will decrease total bundle size by 146.16kB (-0.62%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
App Routes Affected:
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
Updated extrapolation docs for clarity and adding an image to make it clearer how extrapolation works.
Trace Explorer updates: https://sentry-docs-git-extrapolation-doc-improvements.sentry.dev/product/explore/trace-explorer/#how-sampling-affects-queries-in-trace-explorer
Extrapolation concept: https://sentry-docs-git-extrapolation-doc-improvements.sentry.dev/concepts/key-terms/extrapolation/
Logs updates: https://sentry-docs-git-extrapolation-doc-improvements.sentry.dev/product/explore/logs/#viewing-and-searching-logs / query volumes: https://sentry-docs-git-extrapolation-doc-improvements.sentry.dev/product/explore/logs/#query-volumes
developer doc: https://develop-docs-git-extrapolation-doc-improvements.sentry.dev/application-architecture/dynamic-sampling/extrapolation/
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: