-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat(replay): Re-sample sessions after they expire #8407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
size-limit report 📦
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've only taken a quick glance at this, but the approach seems sound to me. Will have to give it a thorough read in the next day or two.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can we test this on sentry.io before merging to master?
We could release an alpha if we're not 100% certain about it! |
9bc0ee3
to
97784ed
Compare
97784ed
to
8350255
Compare
8350255
to
c59d333
Compare
This is a PR to this feature branch: #8407 * Handle edge case where we stop multiple times (honestly no idea how this should happen, but apparently it can 😬 ) * Add some more logging for state changes We can hopefully eventually remove the `traceInternals` checks, but for now this is an easy solution for debugging in the beta....
Close in favor of #8834 |
This PR changes the replay session expiry behavior fundamentally.
Old behavior
New behavior
.start()
or.startBufffering()
(or nothing if both sample rates are 0).This is quite a change and touches a bunch of places, and required changes to a bunch of tests. So although it's a bit hard to review, we should be very careful with this. But overall, it appears to be clearer to me anyhow what is happening.
Closes #8257
Closes #8400