docs: note severity floor in controller runbook - #355
Merged
Conversation
Document the absolute error-rate floor on the critical reconcile-error alert proposed for #326. Critical now requires both a >50% error ratio and roughly one error per minute sustained; the warning tier keeps no floor. A sparse controller failing a handful of orphaned objects pins its ratio at 100% but latches at warning instead of paging on-call. Key changes: - Critical "Meaning" gains the error-rate floor condition - Explain why a sparse permanently-failing controller warns, not pages - Point latched 100%-ratio warnings at the existing orphan guidance
ecv
marked this pull request as ready for review
August 12, 2026 16:57
ecv
enabled auto-merge
August 13, 2026 01:58
scotwells
approved these changes
Aug 13, 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
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.
Runbook companion to #354, the severity-floor proposal for #326.
Updates the controller-health runbook to describe the proposed behavior: the critical tier requires an absolute error rate above roughly one error per minute in addition to the 50% ratio, and a sparse, permanently-failing controller latches at warning instead of paging. Points latched 100%-ratio warnings at the existing orphan guidance.
Hold for #354 agreement.