Repository navigation
fix(sentry): drop expected upstream-outage 503s from capture - #176
Merged
Merged
Conversation
harlan-github-agent
Bot
added
harlan-agent-running
Contributor
Author
🤖 MERGED
GitHub merged this pull request. No further automated Review will run. |
harlan-github-agent
Bot
added
harlan-agent-running
harlan-github-agent
Bot
removed
the
harlan-agent-ready
This was referenced Sep 8, 2026
This was referenced Oct 1, 2026
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.
🔗 Linked issue
Closes #175
❓ Type of change
📚 Description
The weekly Sentry check-in opened this issue. When a skill's upstream is down, the registry handlers answer an intended 503 and record an operational wide event, but Nitro also forwards the thrown error to Sentry as unhandled. So a failure class that is already handled and observed lands a second time, and SKILLD-11 and SKILLD-1E keep growing on it. From the check-in that found it:
The server Sentry config now drops exceptions whose message ends in
unavailable upstream, whether they arrive as the thrown error or as a serialized exception value. The gone-source 410 (Skill source is gone upstream) is a permanent verdict rather than an outage, so it still captures.I matched the shared
unavailable upstreamsuffix instead of the three exact messages, so a future handler reusing the phrasing gets the same drop. If that reads too broad, exact strings are the stricter choice.