What goes into an ML alert runbook?
mediumAnswer
- (1) Alert description + severity.
- (2) Impact assessment: what's affected?
- (3) Diagnostic queries: SQL / Grafana links.
- (4) Common causes + likely fixes.
- (5) Escalation path if diagnostics fail.
- (6) Rollback / mitigation steps.
- (7) Post-mortem template link.
- Stored in wiki / Runhouse / PagerDuty; linked from every alert.
- Rule: every alert must have a runbook; if you can't write one, the alert isn't ready to fire.
Check yourself — multiple choice
- Random
- Alert desc + severity + impact + diagnostic queries + common causes + escalation + rollback steps + post-mortem template; linked from alert; if can't write, alert not ready
- Not needed
- Just log
Runbook: desc + impact + diagnostics + causes + escalation + mitigation.
#observability
Practise MLOps & Data Quality
215 interview questions in this topic.