feat: add classifyError callback for error severity control#8
Open
feat: add classifyError callback for error severity control#8
Conversation
Allow consumers to downgrade errors to warning level instead of only dropping them, so transport errors stay visible in Sentry without triggering high-severity alerts. Bump to v2.1.0.
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.
Summary
classifyErroroptional callback toObservabilityConfigthat returns'drop','warning', orundefinedbeforeSend,'drop'suppresses the error (same asshouldDropError),'warning'downgrades the event level so it won't trigger high-severity alerts, andundefinedleaves it unchangedshouldDropErrorfor backwards compatibility — it takes precedence when both are providedTest plan
classifyErrorreturning'drop'suppresses errorsclassifyErrorreturning'warning'setsevent.level = 'warning'classifyErrorreturningundefinedpasses errors through unchangedshouldDropErrorbehavior is unaffected