Add support for ignoring specific exceptions #14
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.
Summary
This PR adds a new
ignore_exceptionsconfiguration option that allows filtering out specific exception types from being sent to Sentry while still logging them locally via Tracy.Motivation
In production environments with background workers (e.g., Hermes message queue workers), graceful shutdown is triggered via SIGTERM signal during deployments. This causes
ShutdownExceptionto be thrown as part of the normal shutdown process. However, these exceptions were being logged to Sentry, creating noise in error monitoring and making it harder to identify actual issues.Changes
ignore_exceptionsconfig option toSentryExtensionsetIgnoredExceptions()method toSentryLoggerlog()method to skip sending ignored exceptions to SentryUsage
Ignored exceptions will still be logged to Tracy's local log files but won't be sent to Sentry.
Benefits