-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Public API for manual replay control #78018
Comments
@romtsn Is this done? |
@cmanallen only on iOS I think, no other platform |
We should probably add these to the other platforms before GA so that our APIs are consistent. |
If possible, aligning the API for starting/stopping and pausing/resuming SR with continuous profiling could make sense. In other words, those keywords for SR and profiling should do similar things because otherwise, it could confuse users. |
Is it possible to conditionally include replay data in events sent to Sentry using the options.beforeSend callback? Specifically, I'd like to include replay data only for error-level events, while removing it from info, debug, and other non-error event types. What would be the proper approach? |
@rf-westhuizen what SDK? It's a little bit tricky to do that given there's currently no direct connection between error events and replay events (they are send separately in different envelopes, and only being connected through a special envelope header). Do you use |
I'm using sentry_flutter (8.13.0). |
Routing to @getsentry/product-owners-replays for triage ⏲️ |
Similarly to web replays, we should provide public API for controlling replay behavior manually:
start/startBuffering
should start recording a replay regardless of sample rates set, with the corresponding modestop
should stop the replay and send it to sentryflush
should flush all pending segments/frames to sentrystart/stop
current ReplayThere's also interest in permanently deactivating SR after SDK init, e.g. as described here: - getsentry/sentry-cocoa#4833
The text was updated successfully, but these errors were encountered: