Document metric alert rules (metric alerts phase 1) - #71
Merged
Conversation
|
Preview deleted (PR closed). |
New automation/alerts page (metric vocabulary, window semantics, delivery via notification channels, limits) and monitoring.md's Alerting section now points at the built-in rules with external monitoring as the escape hatch.
The create example read as a 10-minute average of CPU. Evaluation requires every present minute-bucket to breach, with an 80%/20% quorum (rounded up), and a single good sample resolves until the window is all-breaching again.
acoshift
force-pushed
the
feat/metric-alerts
branch
from
September 2, 2026 04:45
b251e59 to
f87595c
Compare
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.
Summary
Docs for the new metric alert rules (SPEC-metric-alerts.md Phase 1; api#133, apiserver#249, console#335, deploys#61, mcp#50).
automation/alerts.md(weight 7, right after notification channels): fields, metric vocabulary (% of limit vs per-minute rates), rolling-window firing semantics (80%/20% quorums, nodata-holds-firing, built-in hysteresis), renotify, delivery via notification channels (alert.trigger/alert.resolve), limits, API action names, permissionsdeployments/monitoring.mdAlerting section now leads with the built-in rules; external monitoring kept as the escape hatchFollow-up (blocked on console#335 deploy): add a console screenshot via
scripts/screenshots/refresh.sh.Testing
hugo --minifyclean (60 pages); nav places Alerts after Notifications; cross-links resolve.