Agent skill · product strategy · jeremylongshore
langfuse-incident-runbook
Troubleshoot and respond to Langfuse-related incidents and outages.
Why this skill is useful
Provides specific troubleshooting commands and procedures for Langfuse incidents that the AI wouldn't reliably generate on its own.
What it needs
Requires curl installed locally. Requires langfuse account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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 Instructions Step 1: Initial Assessment (2 Minutes) Step 2: Determine Incident Type and Response Symptom Likely Cause Immediate Action --------- -------------- ----------------- No traces appearing SDK not flushing Check shutdown handlers; set flushAt: 1 temporarily 401 Unauthorized Key rotation or mismatch Verify keys match the correct project 429 Too Many Requests Rate limited Increase batch size, reduce flush frequency SDK throwing errors Unhandled exception Wrap in try/catch; check SDK version High request latency Sync flush in hot path Switch to async; increase requestTimeout Complete Langfuse outage Service-side issue Enable fallback mode Step 3: Fallback Mode (P1 -- App Impacted) If Langfuse is causing application issues, disable tracing immediately: For v3, use the enabled flag: Step 4: Common Resolution Procedures Procedure A: Missing Traces Procedure B: Rate Limit (429) Recovery Procedure C: Self-Hosted Instance Down Step 5: Post-Incident Verification Step 6: Post-Incident Review (P1/P2) Document for post-mortem: …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/langfuse-incident-runbook