AgentSkillsCN

posthog-debug-bundle

收集PostHog调试证据以用于支持工单和故障排除。 在遇到持续问题、准备支持工单或收集PostHog问题的诊断信息时使用。 可通过“posthog debug”、“posthog support bundle”、“collect posthog logs”、“posthog diagnostic”等短语触发。

SKILL.md
--- frontmatter
name: posthog-debug-bundle
description: |
  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", "posthog diagnostic".
allowed-tools: Read, Bash(grep:*), Bash(curl:*), Bash(tar:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>

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

bash
#!/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

bash
# 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

bash
# 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

bash
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.