Repository navigation
fix(landing): sample Sentry session replay at 10% again - #565
Merged
Merged
Conversation
The self-hosted Sentry relay quota fix is live on prod, so envelope bursts above 5/s are no longer rejected. Sentry replay goes back to the T-2008 standard of 1 session in 10, matching PostHog. Error replays stay at 100% and the mask/block selectors are unchanged. Reverts the rate in d2cdf9a while keeping the separate PostHog and Sentry constants.
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
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
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.
Summary
The self-hosted Sentry relay quota fix (#59/#60) is live on prod, so the hold that kept Sentry session replay at 5% (d2cdf9a) is lifted. This puts
SENTRY_REPLAY_SAMPLE_RATEback to the T-2008 standard of 0.1, matching PostHog.replaysOnErrorSampleRatestays 1 (every session with an error keeps its replay).Note: master/prod already runs Sentry at 10% (the 5% change never left dev), so after this merges the pending #561 promotion no longer lowers prod's rate.
Verification
vitest run src/__tests__/sentry-tunnel.test.ts(landing): 19/19 passed, exit 0; the test pinsreplaysSessionSampleRate: 0.1onSentry.initand both constants at 0.1.