-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Replay: Disable session replay if recording affects performance too greatly #8002
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
Hello, we are experiencing similar issue as #6946 for 1 specific form in our angular app. Because of that we had to disable the replays. This would enable us to use them again. When do you plan to release this? |
@Ejdems666 We should have a release by next week, you can keep an eye on #8228 -- I'll be updating docs to reflect on some options while we work on better native solutions, but here are some things you can currently do:
Also if your app is publicly accessible, it'd help me identify additional causes of perf regressions. Feel free to drop me a link if you're interested (billy at sentry.io) - thanks! |
…o regular feature (#8228) Instead of taking a fullsnapshot when `mutationLimit` is reached, lets be aggressive and stop the replay to ensure end-users are not negatively affected performance wise. The default for showing a breadcrumb is at 750 mutations, and the default limit to stop recording is 10000 mutations. Closes #8002
@billyvg Thank you very much for this quick fix. |
We'll attempt to detect Session Replay recording overhead to gracefully downgrade Sentry off of Replay, into Errors and Performance monitoring only (or whatever is configured).
This should address:
The text was updated successfully, but these errors were encountered: