langfuse-incident-runbook
Installation
SKILL.md
Langfuse Incident Runbook
Prerequisites
- Access to the affected Langfuse project, deployment logs, and the service status page.
- An on-call contact and a change path for disabling or reconfiguring telemetry safely.
- A redaction-safe incident record; do not paste API keys, authorization headers, or prompts into it.
Overview
Step-by-step procedures for Langfuse-related incidents, from initial triage (2 min) through resolution and post-incident review. Your application should work without Langfuse -- these procedures focus on restoring observability.
Severity Classification
| Severity | Description | Response Time | Example |
|---|---|---|---|
| P1 | Application impacted by tracing | 15 min | SDK throwing unhandled errors, blocking requests |
| P2 | Traces not appearing, no app impact | 1 hour | Missing observability data |
| P3 | Degraded performance from tracing | 4 hours | High latency from flush backlog |
| P4 | Minor issues | 24 hours | Occasional missing traces |