chore(index_and_notify): use exc_info and logger_context with logger.error#2566
Open
chore(index_and_notify): use exc_info and logger_context with logger.error#2566
Conversation
thenav56
force-pushed
the
fix/sentry-errors
branch
from
04f7fa3 to
40a3fe4
Compare
Member
Author
|
Hey @szabozoltan69, When you have time, please review and merge this PR. It's not urgent, feel free to include it with other important updates to staging/production. This change will group similar this type of errors in Sentry into one error with multiple events: |
szabozoltan69
force-pushed
the
develop
branch
2 times, most recently
from
0392761 to
514e327
Compare
szabozoltan69
force-pushed
the
develop
branch
from
a4f7684 to
4738b32
Compare
szabozoltan69
force-pushed
the
develop
branch
from
f89066e to
f171c69
Compare
szabozoltan69
force-pushed
the
develop
branch
from
c139ea6 to
fe50eaf
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Addresses Sentry grouping issue with "1 document(s) failed to index" error
Sample: https://sentry.northeurope.cloudapp.azure.com/organizations/ifrc-go/issues/5956/?alert_rule_id=2&alert_timestamp=1759894520471&alert_type=email&environment=production¬ification_uuid=d0fc18ff-0549-4d75-b8f3-ffd154fd8408&project=2&referrer=alert_email#contexts
Changes