Collect comprehensive debug information for Deepgram support tickets and troubleshooting. Bundles environment info, API connectivity tests, request logs, audio analysis, and reproduction scripts into a single archive.
Gather system and SDK version information (Node.js, Python, OS, SDK versions).
Verify REST API and WebSocket endpoint reachability with curl against api.deepgram.com.
Use DeepgramDebugger class to log full request/response details with timing and error capture.
Build a standalone script that reproduces the issue with the NASA podcast sample audio.
Run ffprobe analysis on the audio file to verify format, encoding, and duration.
Run collect-debug-bundle.sh to compile environment, connectivity, logs, and audio analysis into a .tar.gz archive.
deepgram-debug-YYYYMMDD-HHMMSS.tar.gz containing:
environment.txt - System and SDK versionsconnectivity.txt - API connectivity test resultsapp-logs.txt - Recent application logs (sanitized)audio-analysis.txt - Audio file details (if provided)README.txt - Bundle description and issue template| Issue | Cause | Resolution |
|---|---|---|
| API connectivity fails | Invalid key or network | Verify DEEPGRAM_API_KEY and network access |
| Empty response | Silent or corrupt audio | Check audio format with ffprobe |
| SDK not found | Missing dependency | Run npm list @deepgram/sdk or pip show deepgram-sdk |
Include: issue summary, environment details, request IDs, steps to reproduce, expected vs actual behavior, and attach the debug bundle archive.
set -euo pipefail
curl -s -o /dev/null -w "%{http_code}" \
-X GET 'https://api.deepgram.com/v1/projects' \
-H "Authorization: Token $DEEPGRAM_API_KEY"
See detailed implementation for advanced patterns.