groq-debug-bundle

Groq Debug Bundle

Overview

Collect all necessary diagnostic information for Groq support tickets.

Prerequisites

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

Instructions

Step 1: Create Debug Bundle Script

#!/bin/bash
# groq-debug-bundle.sh
 
BUNDLE_DIR="groq-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE_DIR"
 
echo "=== Groq 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 "GROQ_API_KEY: ${GROQ_API_KEY:+[SET]}" >> "$BUNDLE_DIR/summary.txt"

Step 3: Gather SDK and Logs

# SDK version
npm list @groq/sdk 2>/dev/null >> "$BUNDLE_DIR/summary.txt"
 
# Recent logs (redacted)
grep -i "groq" ~/.npm/_logs/*.log 2>/dev/null | tail -50 >> "$BUNDLE_DIR/logs.txt"
 
# Configuration (redacted - secrets masked)
echo

Step 4: Package Bundle

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

Output

• groq-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

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 groq-debug-bundle.sh
2. Review for sensitive data
3. Upload to Groq support portal

Resources

• Groq Support
• Groq Status

Next Steps

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