Skip to main content Inicio Creadores jeremylongshore tons-of-skills-marketplace langfuse-debug-bundle
langfuse-debug-bundle Collect Langfuse debug evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for Langfuse problems.
Trigger with phrases like "langfuse debug", "langfuse support bundle",
"collect langfuse logs", "langfuse diagnostic", "langfuse troubleshoot".
Ir a la instalación Skills Marketplace Descubre y explora habilidades de IA creadas por la comunidad.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Mostrar detalles del prompt Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill langfuse-debug-bundleEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Descargar Zip Descargando... Más de este repositorio langchain-deploy-integration Deploy a LangChain 1.0 / LangGraph 1.0 app to Cloud Run, Vercel, or LangServe correctly — with timeouts sized for chain length, cold-start mitigation, SSE anti-buffering headers, and Secret Manager over .env. Use when prepping a first production deploy, debugging a stream that hangs behind a proxy, or diagnosing p99 latency spikes. Trigger with "langchain deploy", "langchain cloud run", "langchain vercel python", "langchain langserve", or "langchain docker".
langchain-langgraph-agents Build a correct LangGraph 1.0 ReAct agent with create_react_agent — typed tools, error propagation, recursion caps, and stop conditions that actually stop. Use when writing a first tool-calling agent, migrating from AgentExecutor or initialize_agent, or diagnosing an agent that loops on vague prompts. Trigger with "langgraph agent", "create_react_agent", "langgraph tool calling", "AgentExecutor migration", or "agent loop cost".
langchain-langgraph-human-in-loop Build LangGraph 1.0 human-in-the-loop approval flows with interrupt_before /
interrupt_after and Command(resume=...) — JSON-serializable state, clean
resume semantics, and UI wiring for approval decisions. Use when adding an
approval gate before an expensive tool call, wiring a Slack/web UI for agent
approvals, or debugging a graph that crashes on interrupt.
Trigger with "langgraph human in loop", "langgraph interrupt_before",
"langgraph approval flow", "Command resume", "langgraph HITL".
name langfuse-debug-bundle description Collect Langfuse debug evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for Langfuse problems.
Trigger with phrases like "langfuse debug", "langfuse support bundle",
"collect langfuse logs", "langfuse diagnostic", "langfuse troubleshoot".
allowed-tools Read, Bash(grep:*), Bash(curl:*), Bash(tar:*), Grep version 1.12.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","langfuse","debugging"] compatibility Designed for Claude Code
Langfuse Debug Bundle
Current State
!node --version 2>/dev/null || echo 'N/A'
!python3 --version 2>/dev/null || echo 'N/A'
!npm list langfuse @langfuse/client @langfuse/tracing 2>/dev/null | head -5 || echo 'No langfuse packages'
Overview
Collect all diagnostic information needed for Langfuse support tickets: environment versions, SDK config, API connectivity, redacted logs, and a reproduction template.
Prerequisites
Langfuse SDK installed
Access to application logs
Bash shell available
Instructions
Step 1: Run the Full Debug Bundle Script
Save this as langfuse-debug.sh and run it:
#!/bin/bash
set -euo pipefail
BUNDLE_DIR="langfuse-debug-$(date +%Y%m%d-%H%M%S) "
mkdir -p "$BUNDLE_DIR "
echo "=== Langfuse Debug Bundle ===" | tee "$BUNDLE_DIR /summary.txt"
echo "Generated: $(date) " | tee -a "$BUNDLE_DIR /summary.txt"
{
echo ""
echo "--- Environment ---"
echo "Node.js: $(node --version 2>/dev/null || echo 'not installed') "
echo "Python: $(python3 --version 2>/dev/null || echo 'not installed') "
echo "npm: $(npm --version 2>/dev/null || echo 'not installed') "
echo "OS: $(uname -srm) "
} >> "$BUNDLE_DIR /summary.txt"
echo
""
echo
"--- SDK Versions ---"
echo
"npm: no langfuse packages"
"Name|Version"
echo
"pip: langfuse not found"
"$BUNDLE_DIR /summary.txt"
echo
""
echo
"--- Langfuse Config ---"
echo
"LANGFUSE_PUBLIC_KEY: ${LANGFUSE_PUBLIC_KEY:+SET (${LANGFUSE_PUBLIC_KEY:0:12} ...)} "
echo
"LANGFUSE_SECRET_KEY: ${LANGFUSE_SECRET_KEY:+SET} "
echo
"LANGFUSE_BASE_URL: ${LANGFUSE_BASE_URL:-NOT SET} "
echo
"LANGFUSE_HOST: ${LANGFUSE_HOST:-NOT SET} "
"$BUNDLE_DIR /summary.txt"
echo
""
echo
"--- Network Test ---"
"${LANGFUSE_BASE_URL:-${LANGFUSE_HOST:-https://cloud.langfuse.com} } "
echo
"Target host: $HOST "
echo
"Health endpoint: "
"%{http_code} (%{time_total}s)"
"$HOST /api/public/health"
echo
"FAILED"
echo
""
if
"${LANGFUSE_PUBLIC_KEY:-} "
"${LANGFUSE_SECRET_KEY:-} "
then
echo
"$LANGFUSE_PUBLIC_KEY :$LANGFUSE_SECRET_KEY "
base64
echo
"Auth test: "
"%{http_code}"
"Authorization: Basic $AUTH "
"$HOST /api/public/traces?limit=1"
echo
"FAILED"
echo
""
fi
"$BUNDLE_DIR /summary.txt"
if
"logs"
then
"langfuse\|trace\|generation\|flush"
log
tail
's/sk-lf-[a-zA-Z0-9]*/sk-lf-***REDACTED***/g'
's/pk-lf-[a-zA-Z0-9]*/pk-lf-***REDACTED***/g'
"$BUNDLE_DIR /app-logs-redacted.txt"
true
fi
if
"package.json"
then
'"dependencies"'
head
"$BUNDLE_DIR /package-deps.txt"
true
fi
cat
"$BUNDLE_DIR /reproduction-steps.md"
'REPRO'
## Relevant Code
```typescript
// Paste minimal reproduction here
--- Package --- tar -czf "$BUNDLE_DIR.tar.gz" "$BUNDLE_DIR" 2>/dev/null
echo ""
echo "Bundle created: $BUNDLE_DIR.tar.gz"
echo "Contents:"
ls -la "$BUNDLE_DIR/"
### Step 2: Review Before Sharing
**Always redact before submitting:**
| Include | Redact |
|---------|--------|
| Error messages and stack traces | API keys (`pk-lf-*`, `sk-lf-*`) |
| SDK versions and config structure | Secret keys and passwords |
| HTTP status codes | PII (emails, user IDs) |
| Timing and latency data | Internal URLs and IPs |
| OS and runtime versions | Database connection strings |
### Step 3: Submit to Support
1. Run: `bash langfuse-debug.sh`
2. Review bundle contents for leaked secrets
3. Fill in `reproduction-steps.md`
4. Submit via:
- [GitHub Issues](https://github.com/langfuse/langfuse/issues) (public)
- [Discord](https://langfuse.com/discord) (community)
- Email support (enterprise customers)
### Step 4: Quick Inline Diagnostic (No File)
For a fast check without creating files:
```bash
set -euo pipefail
echo "=== Quick Langfuse Check ==="
echo "Node: $(node --version 2>/dev/null || echo N/A)"
npm list langfuse @langfuse/client 2>/dev/null | head -5
echo ""
echo "Public Key: ${LANGFUSE_PUBLIC_KEY:+SET} | Secret Key: ${LANGFUSE_SECRET_KEY:+SET}"
HOST="${LANGFUSE_BASE_URL:-${LANGFUSE_HOST:-https://cloud.langfuse.com}}"
echo "Health: $(curl -s -o /dev/null -w '%{http_code}' $HOST/api/public/health)"
Error Handling Collected Item Why It Matters SDK version Version-specific bugs, breaking changes between v3/v4/v5 Environment versions Node 18+ required, Python 3.9+ Network test Firewall, DNS, self-hosted connectivity Auth test Key validity, project mismatch Redacted logs Trace errors, flush failures, rate limits Package deps Conflicting versions, missing peer deps
Resources 