-
Classify severity. Match user impact to the P1–P4 table in
triage-and-diagnostics.md — this sets your response-time budget (P1 < 15 min, P4 next business day).
-
Triage. Run the Quick Triage script (status reachability, auth, per-model availability, rate-limit headers). The one-line probe that starts most incidents:
curl -s -o /dev/null -w "%{http_code}\n" \
https://api.groq.com/openai/v1/models \
-H "Authorization: Bearer $GROQ_API_KEY"
-
Decide. Walk the decision tree in
triage-and-diagnostics.md to turn the HTTP code (timeout / 401 / 429 / 5xx / slow) into an action path.
-
Mitigate. Apply the matching fix from mitigations.md: fallback-model routing for 5xx on one model, wait-or-reroute for 429, key rotation for 401, enable the fallback provider for a Groq-wide outage.
-
Communicate & close. Post the internal alert and status-page update, then after resolution collect evidence and write the postmortem — all in communication-and-postmortem.md.