sentry-known-pitfalls

# Sentry Known Pitfalls ## Overview Ten production-grade Sentry SDK anti-patterns that silently break error tracking, inflate costs, or leave teams blind to failures. Each pitfall includes the broken pattern, root cause, and production-ready fix. For extended code samples and audit scripts, see [configuration pitfalls](references/configuration-pitfalls.md), [error capture pitfalls](references/error-capture-pitfalls.md), [SDK initialization pitfalls](references/sdk-initialization-pitfalls.md), [integration pitfalls](references/integration-pitfalls.md), and [monitoring pitfalls](references/monitoring-pitfalls.md). ## Prerequisites - Active Sentry project with `@sentry/node` >= 8.x or `@sentry/browser` >= 8.x - Access to the codebase containing `Sentry.init()` configuration - Environment variable management (`.env`, secrets manager, or CI/CD vars) ## Instructions ### Step 1: Scan for Existing Pitfalls ```bash # Hardcoded DSNs (Pitfall 1) grep -rn "ingest\.sentry\.io" --include="*.ts" --include="*.js" src/ # 100% sample rates (Pitfall 2) grep -rn "sampleRate.*1\.0" --include="*.ts" --include="*.js" src/ # Missing flush calls (Pitfall 3) grep -rn "Sentry\.flush\|Sentry\.close" --include="*.ts" --include="*.js" src/ # Wrong SDK imports (Pitfall 8) grep -rn "@sentry/node" --include="*.tsx" --include="*.jsx" src/ ``` ### Step 2: Pitfall 1 — Hardcoding DSN in Source Code DSN in source ships in client bundles and cannot be rotated without a deploy. Attackers flood your pro...