Suggested solution to disable RUM initialization for worker #642
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This solution leverages Shared Preferences to initialize the RUM. The default value in Shared preferences is set to true. Thus when the app is launched, the SplunkRum is initialized and whenever worker is enqueued and backgroundService is run in doWork, we change the key in SHaredPreference to false, which is read in Application.java to not initialize RUM.
Lucid chart:
![Uploading Screenshot 2023-09-15 at 10.05.51 AM.png…]()
https://lucid.app/lucidchart/7d8a8cc9-b495-4659-8c41-bc934552745f/edit?view_items=qU5uVi6f-co2&invitationId=inv_c07e838d-c25a-4a24-ad3c-41f9499f66eb