Skip to main content
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".
Jump to install Skills Marketplace Discover and explore AI skills built by the community.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Copy promptShow prompt details A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill langfuse-debug-bundleThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Download Zip Downloading... More from this repository Implement user sign-up and sign-in flows with Clerk.
Use when building authentication UI, customizing sign-in experience,
or implementing OAuth social login.
Trigger with phrases like "clerk sign-in", "clerk sign-up",
"clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk.
Use when managing user sessions, configuring route protection,
or implementing token refresh and custom JWT templates.
Trigger with phrases like "clerk session", "clerk middleware",
"clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management.
Use when implementing SSO integration, configuring role-based permissions,
or setting up organization-level controls.
Trigger with phrases like "clerk SSO", "clerk RBAC",
"clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
Related occupations SOC
Based on SOC occupation classification
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, also compatible with Codex and OpenClaw
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) "
} >>
{
npm list langfuse @langfuse/client @langfuse/tracing @langfuse/otel @langfuse/openai @langfuse/langchain 2>/dev/null ||
pip show langfuse 2>/dev/null | grep -E ||
} >>
{
} >>
{
HOST=
-n
curl -s -o /dev/null -w 2>/dev/null ||
[ -n ] && [ -n ];
AUTH=$( -n | )
-n
curl -s -o /dev/null -w \
-H \
2>/dev/null ||
} >>
[ -d ];
grep -i logs/*. 2>/dev/null | \
-100 | \
sed | \
sed \
> 2>/dev/null ||
[ -f ];
grep -A 100 package.json | -60 > 2>/dev/null ||
> <<
- Node.js version:
- Langfuse SDK version:
- Langfuse host: Cloud / Self-hosted (version: )
1.
2.
3.
"$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