sentry-multi-env-setup

# Sentry Multi-Environment Setup ## Overview Configure Sentry to run across development, staging, and production with isolated DSNs, tuned sample rates, environment-aware alert routing, and dashboard filtering. Covers `@sentry/node` v8+ (TypeScript) and `sentry-sdk` v2+ (Python), targeting `sentry.io` or self-hosted Sentry 24.1+. The goal is to capture everything in dev, validate in staging, and protect production with tight sampling and PII scrubbing. ## Prerequisites - Sentry organization at [sentry.io](https://sentry.io) with at least one project created - `@sentry/node` v8+ installed (`npm install @sentry/node`) or `sentry-sdk` v2+ (`pip install sentry-sdk`) - Environment naming convention agreed upon (this guide uses `development`, `staging`, `production`) - DSN strategy decided: single project with environment tags or separate projects per environment (see [project-structure-options.md](references/project-structure-options.md)) - `.env` file management tooling (dotenv, direnv, or platform-native env config) ## Instructions ### Step 1 — Create Environment-Aware SDK Configuration with Separate DSNs Each environment gets its own DSN pointing to a dedicated Sentry project. This prevents dev noise from inflating production quotas and allows independent rate limits per environment. **Set up `.env` files per environment:** ```bash # .env.development SENTRY_DSN=https://dev-key@o0.ingest.sentry.io/111 SENTRY_ENVIRONMENT=development SENTRY_RELEASE=local-dev # .env.stagi...