Restore Sentry grouping while preserving Papertrail extra context #1365
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.
Closes #1351
I tested the implementation with the following simultaneous calls to the logger:
Here is how the new setup renders messages in the console, Papertrail and Sentry:
Console
Papertrail - mocked through
syslog(with extra contextual information)Sentry (grouped Issues with contextualized Events)
As you can see on the screenshot, even with the extra context (stored in Additional data as before) the messages are still well grouped in Sentry, 1 issue associated with 2 events in the 2 cases.