Skip to content
LiveNew tools this week
Submit
AIMarketly
posthog-debug-bundle logo

PostHog Debug Bundle

posthog-debug-bundle

Collect PostHog debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for PostHog problems. Trigger with phrases like "posthog debug", "posthog support bundle", "collect posthog logs", "post...

HelixDevelopment/HelixAgent0installs0stars

SKILL.md

Full skill instructions

PostHog Debug Bundle

Overview

Collect all necessary diagnostic information for PostHog support tickets.

Prerequisites

  • PostHog SDK installed
  • Access to application logs
  • Permission to collect environment info

Instructions

Step 1: Create Debug Bundle Script

#!/​bin/​bash
# posthog-debug-bundle.sh

BUNDLE_DIR="posthog-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE_DIR"

echo "=== PostHog Debug Bundle ===" > "$BUNDLE_DIR/​summary.txt"
echo "Generated: $(date)" >> "$BUNDLE_DIR/​summary.txt"

Step 2: Collect Environment Info

# Environment info
echo "--- Environment ---" >> "$BUNDLE_DIR/​summary.txt"
node --version >> "$BUNDLE_DIR/​summary.txt" 2>&1
npm --version >> "$BUNDLE_DIR/​summary.txt" 2>&1
echo "POSTHOG_API_KEY: ${POSTHOG_API_KEY:+[SET]}" >> "$BUNDLE_DIR/​summary.txt"

Step 3: Gather SDK and Logs

# SDK version
npm list @posthog/​sdk 2>/​dev/​null >> "$BUNDLE_DIR/​summary.txt"

# Recent logs (redacted)
grep -i "posthog" ~/​.npm/​_logs/​*.log 2>/​dev/​null | tail -50 >> "$BUNDLE_DIR/​logs.txt"

# Configuration (redacted - secrets masked)
echo "--- Config (redacted) ---" >> "$BUNDLE_DIR/​summary.txt"
cat .env 2>/​dev/​null | sed 's/=.*/=***REDACTED***/' >> "$BUNDLE_DIR/​config-redacted.txt"

# Network connectivity test
echo "--- Network Test ---" >> "$BUNDLE_DIR/​summary.txt"
echo -n "API Health: " >> "$BUNDLE_DIR/​summary.txt"
curl -s -o /​dev/​null -w "%{http_code}" https://api.posthog.com/health >> "$BUNDLE_DIR/​summary.txt"
echo "" >> "$BUNDLE_DIR/​summary.txt"

Step 4: Package Bundle

tar -czf "$BUNDLE_DIR.tar.gz" "$BUNDLE_DIR"
echo "Bundle created: $BUNDLE_DIR.tar.gz"

Output

  • posthog-debug-YYYYMMDD-HHMMSS.tar.gz archive containing:
    • summary.txt - Environment and SDK info
    • logs.txt - Recent redacted logs
    • config-redacted.txt - Configuration (secrets removed)

Error Handling

ItemPurposeIncluded
Environment versionsCompatibility check✓
SDK versionVersion-specific bugs✓
Error logs (redacted)Root cause analysis✓
Config (redacted)Configuration issues✓
Network testConnectivity issues✓

Examples

Sensitive Data Handling

ALWAYS REDACT:

  • API keys and tokens
  • Passwords and secrets
  • PII (emails, names, IDs)

Safe to Include:

  • Error messages
  • Stack traces (redacted)
  • SDK/​runtime versions

Submit to Support

  1. Create bundle: bash posthog-debug-bundle.sh
  2. Review for sensitive data
  3. Upload to PostHog support portal

Resources

Next Steps

For rate limit issues, see posthog-rate-limits.