# Prometheus alert review

## Signal
- [ ] Alert represents customer impact, exhaustion or a necessary operator decision
- [ ] PromQL expression is correct across missing, stale and reset series
- [ ] Label matchers select only the intended services and environments
- [ ] Threshold is supported by capacity, SLO or failure evidence

## Timing
- [ ] Evaluation interval and for-duration match the failure timescale
- [ ] Alert resolves when the actionable condition clears
- [ ] Short data gaps do not create misleading recovery or firing loops
- [ ] Expected deployment and maintenance behaviour is accounted for

## Routing and context
- [ ] Ownership labels route to a staffed receiver
- [ ] Summary identifies the affected service and condition
- [ ] Annotations link to a current, permission-accessible runbook
- [ ] Grouping and inhibition avoid notification floods

## Validation
- [ ] promtool validates the rule file
- [ ] Unit tests cover firing, non-firing and missing-data cases
- [ ] A test notification reaches the intended receiver
- [ ] Review date and accountable owner are recorded