Added message name tracking for compatibility with Sentry server, version 8.3.0 #379
Conversation
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
…sion 8.3.0 Sentry server 8.3.0 tracks all events generated by sentry-php as <no message value>. To fix the incompatibility the exception's name has been added to the actual event.
Member
|
I'm not sure what you intended (it got formatted out in the description), but we explicitly do not send the 'message' attribute anymore as its only for legacy events. You'll need to upgrade your sentry server or use an older version of sentry/sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Sentry server 8.3.0 tracks all events generated by sentry-php as .
To fix the incompatibility the exception's name has been added to the actual event.