fix(eap): Remove static sample count thresholds #6892
Merged
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.
The
reliability
flag is supposed to return the mathematical accuracybased on the sample rate without other additional heuristics applied.
Currently, the calculation also compares the sample count with a static
threshold (count > 100) and returns low reliability if the count is
below.
Going forward, any checks for a static sample count threshold will be
performed outside of the EAP.
Confidence calculation for aggregations other than AVG will be fixed in
follow-up PRs.
Requires getsentry/sentry#85323
Ref https://github.com/getsentry/eap-planning/issues/192