Enhance Sentry error fingerprinting #179
Merged
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.
Context
Due to unoptimised fingerprinting in our existing Sentry implementation, many related events are not being grouped together.
By delegating to use the default fingerprinting algorithms in Sentry, with some additional granularity, we might be able to group events better → https://docs.sentry.io/platforms/go/guides/gin/usage/sdk-fingerprinting/
Additionally, we can accept optional parameters to enrich the event → https://docs.sentry.io/platforms/go/guides/gin/enriching-events/
Changes
Introduced a newErrorDatastruct to carry optionalExtraandTagsdata, giving consumers flexibility in including more detailed context in error events.UpdatedCaptureErrorandCaptureWarningfunctions to accept optionalErrorDataparameters, maintaining backward compatibility while enabling additional context to be passed.enrichScopefunction for clarity.Note
This PR initially contained changes that added easier attachment of tags/extras via a new
ErrorDatastruct. To simplify the changes I've since removed them.