feat(metrics): Store sample rates instead of extrapolating #3884
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.
Based on the global option
sentry-metrics.extrapolation.propagate-rates
, Relay ignores the per-project extrapolation config and instead places sample rates on metric buckets to send them into storage. Storage can then at query time choose to ignore these rates or use them for weighting.Since there is no impact on the ingested raw values, this is no longer a project option and completely bypasses the extrapolation config in the project state.
Epic: #3724