Skip to content
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

Feature Request: Remote Config Option for Session Replay Sample Rate in Mobile SDKs #82543

Open
Prithvirajkumar opened this issue Dec 23, 2024 · 3 comments

Comments

@Prithvirajkumar
Copy link
Member

Problem Statement

Customers are testing out Session Replay for their mobile applications.
During testing and potential scaling, they require the option to dynamically adjust the Session Replay sample rate without requiring an app release.

In scenarios where developers need to fine-tune the sample rate based on app performance, user behavior, or infrastructure considerations, rolling out an app update to modify the sample rate is both time-consuming and inefficient.

The proposed solution is for Sentry to provide support for remote configuration of the Session Replay sample rate in the Mobile SDKs.
This feature would allow developers to change the sample rate dynamically via a remote request after SDK initialization.

Remote configuration would provide:

  • Greater flexibility in managing Session Replay settings.
  • Improved ability to scale and test effectively during rollout phases.
  • Reduced operational friction for engineering teams managing frequent changes to sample rates.

Solution Brainstorm

No response

Product Area

Replays

@getsantry
Copy link
Contributor

getsantry bot commented Dec 23, 2024

Routing to @getsentry/product-owners-replays for triage ⏲️

@getsantry
Copy link
Contributor

getsantry bot commented Dec 23, 2024

Auto-routing to @getsentry/product-owners-replays for triage ⏲️

@bruno-garcia
Copy link
Member

The ability to configure the SDK remotely makes a lot of sense, specially on mobile environments.
Thanks for raising.

We have not planned to implement this yet though.
The work around now is to use another service, to get the config before initializing Sentry.
Unfortunately that means that if fetching the config fails, Sentry won't report on that since it happens before Sentry inits/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants