🔊 [RUMF-1345] add telemetry logs on untrusted events #1910
Merged
+89
−21
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
4 tasks
BenoitZugmeyer
changed the title
yannickadam
reviewed
Jan 3, 2023
bcaudan
approved these changes
Jan 3, 2023
yannickadam
approved these changes
Jan 3, 2023
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
We want to better understand what type of untrusted events are being recorded.
Superseds #1878
Changes
Add a telemetry debug log when an untrusted event is dispatched and caught by our SDK. We limit the number of reported events to one per event type to avoid sending too many logs.
Testing
I have gone over the contributing documentation.