sentry-prod-checklist

# Sentry Production Deployment Checklist ## Overview Walk through every production-critical Sentry configuration item before a deploy — SDK init options, source map uploads, alert routing, PII scrubbing, sample rate tuning, and test error verification. Covers `@sentry/node` (v8+) and `sentry-cli` workflows. **Use when:** - Preparing a first production deploy with Sentry - Auditing an existing Sentry config after an incident - Running a go-live readiness review - Onboarding a new service into Sentry monitoring ## Prerequisites - `@sentry/node` (or framework-specific SDK like `@sentry/nextjs`, `@sentry/react`) installed - Sentry project created with a **dedicated production DSN** (separate from dev/staging) - `sentry-cli` installed globally or as a devDependency (`npm i -D @sentry/cli`) - `SENTRY_AUTH_TOKEN` with scope `project:releases` available in CI environment - Build pipeline that produces source maps ## Instructions Work through each section in order. Check off each item as you verify it. ### Step 1 — DSN and Environment Variables - [ ] **DSN set via environment variable, not hardcoded in source code** ```typescript // CORRECT — DSN from environment Sentry.init({ dsn: process.env.SENTRY_DSN, }); // WRONG — hardcoded DSN leaks project ID and org info Sentry.init({ dsn: 'https://abc123@o456.ingest.sentry.io/789', }); ``` Verify with: `grep -r "ingest.sentry.io" src/ --include="*.ts" --include="*.js"` — should return zero results. - [ ] **`SENTRY_DSN` set i...