feat(replay): Send client_report when replay sending fails - #7093
Merged
Conversation
Contributor
size-limit report 📦
|
mydea
force-pushed
the
fn/replay-client-report
branch
from
February 8, 2023 16:03
374be44 to
c6cd14d
Compare
billyvg
approved these changes
Feb 8, 2023
Lms24
approved these changes
Feb 8, 2023
This leverages the new client_report categories.
Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
mydea
force-pushed
the
fn/replay-client-report
branch
from
February 9, 2023 09:19
1761ca8 to
1a08cd9
Compare
This file contains hidden or 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 leverages the new client_report categories.
See getsentry/develop#830
Closes #6774