fix(observer): surface terminal provider circuits - #56
Merged
Conversation
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.
Outcome
Expose durable provider-create retry circuits as bounded observer metrics and fail platform health while a scale set is terminally blocked. Add the exact recovery response to the canonical rules and runbook.
Live trigger
A repaired provider remained unable to serve
nddev-linux-fastbecause eight earlier canary failures left its scale-set domain terminal for 24 hours. The exact existing CAS recovery restored provider create immediately; this change makes that state visible and actionable before queue latency is the only symptom.Verification
make verify