firecrawl-incident-runbook
Installation
SKILL.md
FireCrawl Incident Runbook
Overview
Rapid incident response procedures for FireCrawl-related outages.
Prerequisites
- Access to FireCrawl dashboard and status page
- kubectl access to production cluster
- Prometheus/Grafana access
- Communication channels (Slack, PagerDuty)
Severity Levels
| Level | Definition | Response Time | Examples |
|---|---|---|---|
| P1 | Complete outage | < 15 min | FireCrawl API unreachable |
| P2 | Degraded service | < 1 hour | High latency, partial failures |
| P3 | Minor impact | < 4 hours | Webhook delays, non-critical errors |
| P4 | No user impact | Next business day | Monitoring gaps |