sentry-common-errors

# Sentry Common Errors ## Overview Diagnose and fix the most frequently encountered Sentry SDK integration issues across Node.js, browser, and Python environments. Covers DSN validation, missing events, source map failures, rate limiting, SDK initialization ordering, serverless flush patterns, CORS configuration, and environment tagging. ## Prerequisites - Sentry SDK installed (`@sentry/node` v8+, `@sentry/browser` v8+, or `sentry-sdk` for Python) - Access to Sentry dashboard with project admin or member role - Application logs available for inspection - `sentry-cli` installed for source map and release operations ## Instructions ### Step 1 — Detect the installed SDK and current configuration !`npm list @sentry/node @sentry/browser @sentry/react @sentry/nextjs 2>/dev/null | head -10 || echo "No Node.js Sentry SDK found"` !`python3 -c "import sentry_sdk; print(f'sentry-sdk {sentry_sdk.VERSION}')" 2>/dev/null || echo "No Python sentry-sdk found"` !`command -v sentry-cli >/dev/null && sentry-cli --version || echo "sentry-cli not installed"` Grep the project for Sentry initialization to identify the current configuration: ```bash grep -rn "Sentry.init\|sentry_sdk.init" --include="*.ts" --include="*.js" --include="*.mjs" --include="*.py" . 2>/dev/null | head -20 ``` ### Step 2 — DSN not set or invalid DSN format The DSN (Data Source Name) tells the SDK where to send events. Format: `https://<public-key>@<org>.ingest.sentry.io/<project-id>` **Symptoms:** No events arr...