17 lines
765 B
Markdown
17 lines
765 B
Markdown
|
# Alert review checklist
|
||
|
|
|
||
|
|
For every alert, record:
|
||
|
|
|
||
|
|
1. User impact or operator action the alert demands.
|
||
|
|
2. Metric type: counter, gauge, timestamp, state marker, or recording rule.
|
||
|
|
3. Scope and deduplication labels.
|
||
|
|
4. Persistence window and startup grace.
|
||
|
|
5. Minimum sample size for ratios.
|
||
|
|
6. No-data and query-error behavior.
|
||
|
|
7. Current value and a recent range query.
|
||
|
|
8. Notification frequency in Grafana logs.
|
||
|
|
9. Current, migrated, suspended, or historical resource status.
|
||
|
|
10. Exact Flux-tracked source, generated artifacts, tests, and rollback condition.
|
||
|
|
|
||
|
|
A rule is useful only when its firing state implies a specific human action. Backlogs and unenrolled resources belong on dashboards unless they have crossed an explicitly accepted operational deadline.
|