Skip to main content Accueil Créateurs jeremylongshore tons-of-skills-marketplace sentry-debug-bundle
sentry-debug-bundle Collect diagnostic information for Sentry troubleshooting and support tickets.
Use when events are not appearing in Sentry, SDK initialization seems broken,
DSN connectivity fails, source maps are not resolving, or preparing a support request.
Trigger with "sentry debug info", "sentry diagnostics", "debug bundle", "sentry support ticket".
Aller à l'installation Skills Marketplace Découvrez et explorez les compétences IA créées par la communauté.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Afficher les détails du prompt Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill sentry-debug-bundleLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Télécharger Zip Téléchargement... Explorateur de fichiers
6 fichiers Plus depuis ce dépôt langchain-deploy-integration Deploy a LangChain 1.0 / LangGraph 1.0 app to Cloud Run, Vercel, or LangServe correctly — with timeouts sized for chain length, cold-start mitigation, SSE anti-buffering headers, and Secret Manager over .env. Use when prepping a first production deploy, debugging a stream that hangs behind a proxy, or diagnosing p99 latency spikes. Trigger with "langchain deploy", "langchain cloud run", "langchain vercel python", "langchain langserve", or "langchain docker".
langchain-langgraph-agents Build a correct LangGraph 1.0 ReAct agent with create_react_agent — typed tools, error propagation, recursion caps, and stop conditions that actually stop. Use when writing a first tool-calling agent, migrating from AgentExecutor or initialize_agent, or diagnosing an agent that loops on vague prompts. Trigger with "langgraph agent", "create_react_agent", "langgraph tool calling", "AgentExecutor migration", or "agent loop cost".
langchain-langgraph-human-in-loop Build LangGraph 1.0 human-in-the-loop approval flows with interrupt_before /
interrupt_after and Command(resume=...) — JSON-serializable state, clean
resume semantics, and UI wiring for approval decisions. Use when adding an
approval gate before an expensive tool call, wiring a Slack/web UI for agent
approvals, or debugging a graph that crashes on interrupt.
Trigger with "langgraph human in loop", "langgraph interrupt_before",
"langgraph approval flow", "Command resume", "langgraph HITL".
name sentry-debug-bundle description Collect diagnostic information for Sentry troubleshooting and support tickets.
Use when events are not appearing in Sentry, SDK initialization seems broken,
DSN connectivity fails, source maps are not resolving, or preparing a support request.
Trigger with "sentry debug info", "sentry diagnostics", "debug bundle", "sentry support ticket".
allowed-tools Read, Write, Edit, Bash(npm:*), Bash(node:*), Bash(npx:*), Bash(pip:*), Bash(python:*), Bash(curl:*), Bash(dig:*), Bash(sentry-cli:*), Grep, Glob version 1.51.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","sentry","debugging","support","diagnostics"] compatibility Designed for Claude Code
Sentry Debug Bundle
Overview
Collect SDK versions, configuration state, network connectivity, and event delivery status into a single diagnostic report. Attach the output to Sentry support tickets or use it to systematically isolate why events are not reaching the dashboard.
Current State
!node --version 2>/dev/null || echo 'Node.js not found'
!python3 --version 2>/dev/null || echo 'Python3 not found'
!npm list @sentry/node @sentry/browser @sentry/react @sentry/cli 2>/dev/null | grep sentry || pip show sentry-sdk 2>/dev/null | grep -E '^(Name|Version)' || echo 'No Sentry SDK found'
!sentry-cli --version 2>/dev/null || echo 'sentry-cli not installed'
!sentry-cli info 2>/dev/null || echo 'sentry-cli not authenticated'
Prerequisites
At least one Sentry SDK installed (@sentry/node, @sentry/browser, @sentry/react, or sentry-sdk for Python)
SENTRY_DSN environment variable set (or DSN configured in application code)For API checks: SENTRY_AUTH_TOKEN with project:read scope (generate token )
Optional: sentry-cli installed for source map diagnostics and send-event tests
Instructions
Step 1 — Gather SDK Version, Configuration, and Init Hooks
Identify the installed SDK, verify all @sentry/* packages share the same version (mismatches cause silent failures), and extract the runtime configuration.
Check installed packages:
npm ls @sentry/node @sentry/browser @sentry/react @sentry/nextjs @sentry/cli 2>/dev/null | grep sentry
pip show sentry-sdk 2>/dev/null
Extract runtime configuration (Node.js):
import * as Sentry from '@sentry/node' ;
const client = Sentry .getClient
if
console
error
'ERROR: Sentry client not initialized — Sentry.init() may not have been called'
exit
1
const
getOptions
const
sdk_version
Sentry
SDK_VERSION
dsn_configured
dsn
dsn_host
dsn
new
URL
dsn
hostname
'N/A'
dsn_project_id
dsn
new
URL
dsn
pathname
replace
'/'
''
'N/A'
environment
environment
'(default)'
release
release
'(auto-detect)'
debug
debug
false
sample_rate
sampleRate
1.0
traces_sample_rate
tracesSampleRate
'(not set)'
profiles_sample_rate
profilesSampleRate
'(not set)'
send_default_pii
sendDefaultPii
false
max_breadcrumbs
maxBreadcrumbs
100
before_send
typeof
beforeSend
'function'
'CONFIGURED'
'none'
before_send_transaction
typeof
beforeSendTransaction
'function'
'CONFIGURED'
'none'
before_breadcrumb
typeof
beforeBreadcrumb
'function'
'CONFIGURED'
'none'
integrations
getOptions
integrations
map
i =>
name
transport
transport
'custom'
'default'
console
log
JSON
stringify
null
2
Extract runtime configuration (Python):
import sentry_sdk
from sentry_sdk import Hub
client = Hub.current.client
if not client:
print ("ERROR: Sentry client not initialized" )
exit(1 )
opts = client.options
print (f"SDK version: {sentry_sdk.VERSION} " )
print (f"DSN configured: {bool (opts.get('dsn' ))} " )
print (f"Environment: {opts.get('environment' , '(default)' )} " )
print (f"Release: {opts.get('release' , '(auto-detect)' )} " )
print (f"Debug: {opts.get('debug' , False )} " )
print (f"Sample rate: {opts.get('sample_rate' , 1.0 )} " )
print (f"Traces sample rate:{opts.get('traces_sample_rate' , '(not set)' )} " )
print (f"Send default PII: {opts.get('send_default_pii' , False )} " )
print (f"before_send: {'CONFIGURED' if opts.get('before_send' ) else 'none' } " )
print (f"before_breadcrumb: {'CONFIGURED' if opts.get('before_breadcrumb' ) else 'none' } " )
print (f"Integrations: {[i.identifier for i in client.integrations.values()]} " )
Key check: If beforeSend is CONFIGURED, inspect the function — a beforeSend that returns null will silently drop every event.
Step 2 — Verify DSN Connectivity and Sentry Service Status Confirm the application can reach Sentry's ingest endpoint and that Sentry itself is operational.
curl -s -o /dev/null -w "sentry.io API: HTTP %{http_code} (%{time_total}s)\n" \
https://sentry.io/api/0/
curl -s -o /dev/null -w "Ingest endpoint: HTTP %{http_code} (%{time_total}s)\n" \
"https://o0.ingest.sentry.io/api/0/envelope/"
dig +short o0.ingest.sentry.io 2>/dev/null || nslookup o0.ingest.sentry.io
curl -v https://sentry.io/api/0/ 2>&1 | grep -iE 'proxy|blocked|forbidden|connect'
Check Sentry service status:
curl -s https://status.sentry.io/api/v2/status.json | python3 -c "
import sys, json
d = json.load(sys.stdin)
print(f\"Sentry Status: {d['status']['description']}\")
print(f\"Updated: {d['page']['updated_at']}\")
"
Verify auth token and project access (requires SENTRY_AUTH_TOKEN):
curl -s -H "Authorization: Bearer $SENTRY_AUTH_TOKEN " \
https://sentry.io/api/0/projects/ | python3 -c "
import sys, json
projects = json.load(sys.stdin)
if isinstance(projects, dict) and 'detail' in projects:
print(f'Auth error: {projects[\"detail\"]}')
else:
for p in projects[:10]:
print(f\" {p['organization']['slug']}/{p['slug']} (platform: {p.get('platform', 'N/A')})\")"
sentry-cli info 2>/dev/null || echo "sentry-cli not authenticated — run: sentry-cli login"
Step 3 — Test Event Capture, Verify Delivery, and Generate Report Send a diagnostic test event, confirm it arrives in Sentry, and produce the final debug bundle report.
Send test event via sentry-cli:
sentry-cli send-event -m "diagnostic test from debug-bundle $(date -u +%Y-%m-%dT%H:%M:%SZ) "
Send test event programmatically (Node.js):
import * as Sentry from '@sentry/node' ;
Sentry .init ({
dsn : process.env .SENTRY_DSN ,
debug : true ,
});
const eventId = Sentry .captureMessage ('sentry-debug-bundle diagnostic test' , 'info' );
console .log (`Test event ID: ${eventId} ` );
console .log (`View at: https://sentry.io/organizations/YOUR_ORG/issues/?query=${eventId} ` );
const flushed = await Sentry .flush (10000 );
console .log (`Flush: ${flushed ? 'SUCCESS — event delivered' : 'TIMEOUT — event may not have been sent' } ` );
if (!flushed) {
console .error ('Flush timeout. Possible causes:' );
console .error (' - Network blocking outbound HTTPS to sentry.io' );
console .error (' - DSN is invalid or project has been deleted' );
console .error (' - Rate limit exceeded (HTTP 429)' );
}
Send test event programmatically (Python):
import sentry_sdk
import time
sentry_sdk.init(dsn="YOUR_DSN" , debug=True )
event_id = sentry_sdk.capture_message("sentry-debug-bundle diagnostic test" , level="info" )
print (f"Test event ID: {event_id} " )
sentry_sdk.flush(timeout=10 )
print ("Flush complete — check Sentry dashboard for event" )
Generate the debug bundle report:
#!/bin/bash
set -euo pipefail
REPORT="sentry-debug-$(date +%Y%m%d-%H%M%S) .md"
cat > "$REPORT " << 'HEADER'
HEADER
cat >> "$REPORT " << EOF
**Generated:** $(date -u +"%Y-%m-%dT%H:%M:%SZ")
**Node.js:** $(node --version 2>/dev/null || echo N/A)
**Python:** $(python3 --version 2>/dev/null || echo N/A)
**OS:** $(uname -srm)
**sentry-cli:** $(sentry-cli --version 2>/dev/null || echo 'not installed')
## SDK Packages
\`\`\`
$(npm list 2>/dev/null | grep -i sentry || echo "No npm Sentry packages")
$(pip show sentry-sdk 2>/dev/null | grep -E '^(Name|Version|Location)' || echo "No pip sentry-sdk")
\`\`\`
## Environment Variables (sanitized)
| Variable | Status |
|----------|--------|
| SENTRY_DSN | $([ -n "${SENTRY_DSN:-}" ] && echo "SET (\`$(echo "$SENTRY_DSN" | sed 's|//[^@]*@|//***@|')\`)" || echo "NOT SET") |
| SENTRY_ORG | ${SENTRY_ORG:-NOT SET} |
| SENTRY_PROJECT | ${SENTRY_PROJECT:-NOT SET} |
| SENTRY_AUTH_TOKEN | $([ -n "${SENTRY_AUTH_TOKEN:-}" ] && echo "SET (${#SENTRY_AUTH_TOKEN} chars)" || echo "NOT SET") |
| SENTRY_RELEASE | ${SENTRY_RELEASE:-NOT SET} |
| SENTRY_ENVIRONMENT | ${SENTRY_ENVIRONMENT:-NOT SET} |
| NODE_ENV | ${NODE_ENV:-NOT SET} |
## Network Connectivity
$(curl -s -o /dev/null -w "- sentry.io API: HTTP %{http_code} (%{time_total}s)" https://sentry.io/api/0/ 2>/dev/null || echo "- sentry.io: UNREACHABLE")
$(curl -s -o /dev/null -w "\n- Ingest endpoint: HTTP %{http_code} (%{time_total}s)" https://o0.ingest.sentry.io/api/0/envelope/ 2>/dev/null || echo "- Ingest: UNREACHABLE")
## Sentry Status
$(curl -s https://status.sentry.io/api/v2/status.json 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); print(f\"- Status: {d['status']['description']}\")" 2>/dev/null || echo "- Status: Could not fetch")
## CLI Authentication Status
\`\`\`
$(sentry-cli info 2>/dev/null || echo "sentry-cli not authenticated — run: sentry-cli login")
\`\`\`
## Source Map Artifacts
\`\`\`
$(sentry-cli releases files "${SENTRY_RELEASE:-unknown}" list 2>/dev/null || echo "No release artifacts found (set SENTRY_RELEASE)")
\`\`\`
EOF
echo "Debug bundle saved to: $REPORT "
echo "Attach this file to your Sentry support ticket at https://sentry.io/support/"
Output The debug bundle produces:
SDK inventory — all @sentry/* or sentry-sdk versions with mismatch detectionConfiguration snapshot — DSN (redacted), environment, release, sample rates, hooks statusConnectivity report — HTTP status and latency to sentry.io API and ingest endpointsService status — current Sentry platform health from status.sentry.ioTest event confirmation — event ID with flush result (SUCCESS or TIMEOUT)Markdown report file — sentry-debug-YYYYMMDD-HHMMSS.md ready to attach to support tickets
Error Handling Error Cause Solution Sentry client not initializedSentry.init() not called or called after diagnostic codeEnsure Sentry.init() runs at application entry point before any capture calls Flush: TIMEOUTNetwork blocking outbound HTTPS to *.ingest.sentry.io Check firewall rules, corporate proxy, VPN — allow outbound 443 to *.ingest.sentry.io sentry-cli info reports no authToken not set or expired Run sentry-cli login or set SENTRY_AUTH_TOKEN (generate ) Package version mismatch (@sentry/* at different versions) Partial upgrade or transitive dependency conflict Align all @sentry/* packages to the same version: npm i @sentry/node@latest @sentry/browser@latest and run npm dedupe sourcemaps explain shows no match--url-prefix does not match the stack trace URLsCompare the abs_path in your error event's stack frame with the --url-prefix used during upload Events dropped by beforeSend Hook returns null for matching events Log inside beforeSend to verify: console.log('beforeSend:', event.exception?.values?.[0]?.type) DSN returns HTTP 401 / 403 Project deleted, DSN revoked, or wrong organization Verify DSN at Settings > Projects > Client Keys in the Sentry dashboard 429 Too Many RequestsOrganization or project rate limit exceeded Check quotas at Settings > Subscription, reduce sampleRate/tracesSampleRate, or use beforeSend to filter noise Process exits before events sent (Node.js) No await Sentry.flush() before process.exit() Always call await Sentry.flush(timeout) before exiting; in serverless, use the platform's Sentry.wrapHandler()
Examples
TypeScript — Full Diagnostic Script
import * as Sentry from '@sentry/node' ;
async function runDiagnostics (const client = Sentry .getClient ();
if (!client) {
console .error ('[FAIL] Sentry client not initialized' );
console .error (' Ensure Sentry.init({ dsn: "..." }) is called before this script' );
return ;
}
console .log (`[OK] SDK version: ${Sentry.SDK_VERSION} ` );
const opts = client.getOptions ();
console .log (`[OK] DSN configured: ${!!opts.dsn} ` );
console .log (`[INFO] Environment: ${opts.environment ?? '(default)' } ` );
console .log (`[INFO] Release: ${opts.release ?? '(auto-detect)' } ` );
console .log (`[INFO] Debug mode: ${opts.debug ?? false } ` );
console .log (`[INFO] Sample rate: ${opts.sampleRate ?? 1.0 } ` );
console .log (`[INFO] Traces sample rate: ${opts.tracesSampleRate ?? '(not set)' } ` );
console .log (`[INFO] beforeSend: ${typeof opts.beforeSend === 'function' ? 'CONFIGURED' : 'none' } ` );
const integrations = opts.integrations ?.map (i =>name ) ?? [];
console .log (`[INFO] Integrations (${integrations.length} ): ${integrations.join(', ' )} ` );
const eventId = Sentry .captureMessage ('sentry-diagnostics test event' , 'info' );
console .log (`[INFO] Test event ID: ${eventId} ` );
const flushed = await Sentry .flush (10000 );
if (flushed) {
console .log ('[OK] Flush succeeded — event delivered to Sentry' );
} else {
console .error ('[FAIL] Flush timed out — check network connectivity to Sentry' );
}
}
runDiagnostics ().catch (err =>console .error ('[FAIL] Diagnostic error:' , err));
Python — Full Diagnostic Script
import sentry_sdk
from sentry_sdk import Hub
import urllib.request
import json
import sys
def run_diagnostics ():
print ("=== Sentry Debug Bundle (Python) ===\n" )
print (f"SDK version: {sentry_sdk.VERSION} " )
client = Hub.current.client
if not client:
print ("[FAIL] Sentry client not initialized" )
print (" Call sentry_sdk.init(dsn='...') before running diagnostics" )
sys.exit(1 )
print ("[OK] Client initialized" )
opts = client.options
print (f"[INFO] DSN configured: {bool (opts.get('dsn' ))} " )
print (f"[INFO] Environment: {opts.get('environment' , '(default)' )} " )
print (f"[INFO] Release: {opts.get('release' , '(auto-detect)' )} " )
print (f"[INFO] Debug: {opts.get('debug' , False )} " )
print (f"[INFO] Sample rate: {opts.get('sample_rate' , 1.0 )} " )
print (f"[INFO] Traces sample rate: {opts.get('traces_sample_rate' , '(not set)' )} " )
print (f"[INFO] before_send: {'CONFIGURED' if opts.get('before_send' ) else 'none' } " )
print (f"[INFO] before_breadcrumb: {'CONFIGURED' if opts.get('before_breadcrumb' ) else 'none' } " )
integrations = [i.identifier for i in client.integrations.values()]
print (f"[INFO] Integrations ({len (integrations)} ): {', ' .join(integrations)} " )
try :
req = urllib.request.urlopen("https://sentry.io/api/0/" , timeout=5 )
print (f"[OK] sentry.io reachable (HTTP {req.status} )" )
except Exception as e:
print (f"[FAIL] sentry.io unreachable: {e} " )
try :
req = urllib.request.urlopen("https://status.sentry.io/api/v2/status.json" , timeout=5 )
data = json.loads(req.read())
print (f"[INFO] Sentry status: {data['status' ]['description' ]} " )
except Exception:
print ("[WARN] Could not fetch Sentry status" )
event_id = sentry_sdk.capture_message("sentry-diagnostics test event" , level="info" )
print (f"[INFO] Test event ID: {event_id} " )
sentry_sdk.flush(timeout=10 )
print ("[OK] Flush complete" )
if __name__ == "__main__" :
run_diagnostics()
Resources
Next Steps After collecting the debug bundle:
Events missing? Check beforeSend hook — add logging to confirm events are not being droppedSource maps broken? Run sentry-cli sourcemaps explain --org ORG --project PROJ EVENT_ID to diagnose URL prefix mismatchesPerformance data missing? Verify tracesSampleRate is non-zero and the instrumentation integration is activeRate limited? Review org quotas at Settings > Subscription and reduce sample ratesNeed deeper tracing? Enable debug: true in Sentry.init() to see full SDK lifecycle in consoleReady to file a ticket? Attach the generated sentry-debug-*.md file to your request at sentry.io/support 