triage-alert
Overview
Turns a raw alert into a severity, a blast radius, and the first three things to do.
Instructions
- Read
references/severity-matrix.mdfirst. Severity is decided by the matrix, never by feel. The matrix also carries override rules that beat the error-rate rows outright — you cannot get severity right without reading them. - State the blast radius: what share of traffic or which customers are
affected. If the alert doesn't say, write
unknown. - Assign the severity and quote the matrix row or rule you matched.
- Give the first three actions, most reversible first.
- State whether a status-page update is required, per the matrix.
Output format
Severity: SEV<n> — matched: <the row or rule you applied>
Blast radius: <share of traffic or customers, or "unknown">
Status page: <required within N min | not required>
First actions:
1. <most reversible>
2. ...
3. ...
Edge cases
- Symptom sits between two rows → round up, never down.
- Several symptoms at once → triage the worst one, and note the others.
- No error rate given → say so and triage on the remaining evidence.