deepgram-incident-runbook

# Deepgram Incident Runbook ## Overview Standardized incident response for Deepgram-related production issues. Includes automated triage script, severity classification (SEV1-SEV4), immediate mitigation actions, fallback activation, and post-incident review template. ## Quick Reference | Resource | URL | |----------|-----| | Deepgram Status | https://status.deepgram.com | | Deepgram Console | https://console.deepgram.com | | Support Email | support@deepgram.com | | Community | https://github.com/orgs/deepgram/discussions | ## Severity Classification | Level | Definition | Response Time | Example | |-------|------------|---------------|---------| | SEV1 | Complete outage, all transcriptions failing | Immediate | 100% 5xx errors | | SEV2 | Major degradation, >50% error rate | < 15 min | Specific model failing | | SEV3 | Minor degradation, elevated latency | < 1 hour | P95 > 30s | | SEV4 | Single feature affected, cosmetic | < 24 hours | Diarization inaccurate | ## Instructions ### Step 1: Automated Triage (First 5 Minutes) ```bash #!/bin/bash set -euo pipefail echo "=== Deepgram Incident Triage ===" echo "Timestamp: $(date -u +%Y-%m-%dT%H:%M:%SZ)" echo "" # 1. Check Deepgram status page echo "--- Status Page ---" STATUS=$(curl -s -o /dev/null -w "%{http_code}" https://status.deepgram.com) echo "Status page: HTTP $STATUS" # 2. Test API connectivity echo "" echo "--- API Connectivity ---" curl -s -w "\nHTTP: %{http_code} | Latency: %{time_total}s\n" \ 'https://api.dee...