Instrument LOG_EXCEPTION to observe a new Sentry disposition exception detail - #7185
Open
jtolio wants to merge 1 commit into
Open
Instrument LOG_EXCEPTION to observe a new Sentry disposition exception detail#7185jtolio wants to merge 1 commit into
jtolio wants to merge 1 commit into
Conversation
Contributor
|
I'm Bonk, and I've done a quick review of your PR. Adds Sentry disposition details to
|
…n detail This will allow us to set NOSENTRY or SENTRY_DO or SENTRY_RT or similar on specific messages, designating how we handle these errors or what development team they go to, without adding strings to exception messages. Also tie wdErrId fields more directly to the appropriate name.
jtolio
force-pushed
the
jolio/instrument-l-lziro4
branch
from
August 29, 2026 04:06
7004dd4 to
926896e
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
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.
This will allow us to set NOSENTRY or SENTRY_DO or SENTRY_RT or similar on specific messages, designating how we handle these errors or what development team they go to, without adding strings to exception messages.
Also tie wdErrId fields more directly to the appropriate name.