Skip to content

docs: propose severity floor for error-ratio alerts - #354

Merged
ecv merged 1 commit into
mainfrom
docs/326-severity-floor-proposal
Aug 14, 2026
Merged

docs: propose severity floor for error-ratio alerts#354
ecv merged 1 commit into
mainfrom
docs/326-severity-floor-proposal

Conversation

@ecv

@ecv ecv commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Proposal for the remaining half of #326: ControllerReconcileErrorRatioCritical pages with the same urgency for a controller retrying three orphaned objects as for one failing hundreds of reconciles of live traffic, because the ratio has no notion of volume.

This enhancement gates the critical tier on an absolute error-rate floor (~1 error/minute over the 30m window) in addition to the 50% ratio. Below the floor the same condition fires the warning tier, which keeps no floor: a broken-but-idle controller stays visible and latched without paging. The doc derives the floor from the cases measured on #326, plans promtool fixtures pinning both sides of it, and records why a minimum-denominator guard was rejected.

Docs-only; the rule, fixture, and runbook changes follow once this is agreed.

Add an enhancement proposal for the remaining half of #326: gate
ControllerReconcileErrorRatioCritical on an absolute error-rate floor
(~1 error/minute) in addition to the 50% ratio, so a sparse controller
failing a handful of permanently-failing objects fires a latched warning
instead of paging on-call. The warning tier keeps no floor, so
broken-but-idle controllers stay visible.

Key changes:
- Measured cases from #326 motivate the floor and its default value
- Fixture plan pins both sides of the floor in promtool tests
- Explicitly rejects the minimum-denominator guard with the #326 data
@ecv

ecv commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

Runbook companion: #355

@ecv
ecv merged commit e79f1b7 into main Aug 14, 2026
13 of 15 checks passed
@ecv
ecv deleted the docs/326-severity-floor-proposal branch August 14, 2026 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants