No longer send event / transaction to Sentry if beforeSend
/ beforeSendTransaction
throws
#2591
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.
📜 Description
If an exception occurs in
beforeSend
orbeforeSendTransaction
we no longer send the event / transaction to Sentry.💡 Motivation and Context
Closes #2280 as we no longer want to send an event / transaction in case
beforeSend
/beforeSendTransaction
throws. The reason is that these callbacks are commonly used to filter data before sending to Sentry. In case this filtering logic fails we prefer to not send the event as it may contain sensitive data that was not meant to be sent to Sentry. This also aligns with other Sentry SDKs.💚 How did you test it?
Updated unit tests
📝 Checklist
sendDefaultPII
is enabled.🔮 Next steps