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.
For #1060
We register a sentry event processor and only process events with level error
captureMessage
events pass through the same processor and can have multiple levels.We also don't want to change existing behaviour since this could be a high event volume change for people
So this change allows people to opt-in by setting an allowlist of severity levels to capture
You could set
'*'
to process any sentry messageOr
['error', 'info']
to process default calls tocaptureException
andcaptureMessage
I did consider changing the emitted event so that
captureMessage
did not emit$exception
but insteadevent.message
as the event but it seems neater that the sentry integration always emits the same event typemessage from
captureMessage
enhanced with PostHog URLs