-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Restart onError sampling for replays after stopping #77458
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
Comments
Assigning to @getsentry/support for routing ⏲️ |
Routing to @getsentry/product-owners-replays for triage ⏲️ |
I didn’t make many changes to the version that allowed the use of setupOnce(). In the old version, I used replay.setupOnce() followed by replay.startBuffering(), which successfully reopened a replay after executing replay.stop(). However, after upgrading, I found that setupOnce() is no longer available, and simply executing replay.startBuffering() or replay.start() does not start a new replay. I couldn’t find a solution for this in the documentation. |
@Zero-ruan This is a bit hacky because it's using a private method, but you can call this after switching users: |
Uh oh!
There was an error while loading. Please reload this page.
Problem Statement
We received the following message from a customer:
One account in our team has multiple roles that can be switched. We hope that when the user switches roles, the errors that occur will be recorded in a new Replays.
The latest version does not have replay.setupOnce(). Simply using replay.stop() and replay.start() will not generate new Replays. I only want to use replaysOnErrorSampleRate, because if replaysSessionSampleRate or tracesSampleRate is used, replay.start() will be executed when switching users, and then a Replay without error records will be generated.
Solution Brainstorm
Expose a public API to allow for restarting of onError sampling after replay has been stopped.
Product Area
Replays
The text was updated successfully, but these errors were encountered: