-
Notifications
You must be signed in to change notification settings - Fork 64
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
Disable RUM at runtime #1367
Comments
Hello @fleficher! Thanks for sharing this suggestion. Indeed, we are aware that it might be the need to enable/disable features dynamically, especially in the apps which heavily rely on the remote config. We are working on the changes which should allow to support this use case. It should be available in the SDK v2 which we are going to release soon. |
I see that there are a couple betas of SDK v2! Is this feature supported in there? |
Hello @ankushg! Indeed we have few betas for SDK v2, but the possibility to stop individual features won't be there for With SDK v2 currently you have a possibility to stop the SDK completely, by calling |
Thanks -- that's not exactly what we'd like to do, but looking forward to per-feature (and specifically, RUM) disabling |
Hey @0xnm , Just wanted to know the status of having dedicated consent for RUM on apps? |
@bill350 This is not on our roadmap, data collection rules are not specific to any feature. |
Is your feature request related to a problem? Please describe.
As of today, disabling RUM on the fly is not possible as it requires the user to restart the app to take in effect.
The feature can only be disabled from the
initialize
call which is only working once:The
TrackingConsent
property is used to disable RUM but also logs, etc. We would like to be able to only disable RUM, but not logs.Describe the solution you'd like
Using the same way as for updating the tracking consent:
which will take effect instantly.
The text was updated successfully, but these errors were encountered: