Sentry DSN Configurator

A DSN (Data Source Name) is the connection string that tells the Sentry SDK where to send error reports. It encodes your Sentry organization, project, and an access key. The DSN is safe to include in client-side code — it can only submit events, not read them. Format: https://<key>@<org>.ingest.sentry.io/<project-id>.

tracesSampleRate controls what percentage of transactions (page loads, API calls) are traced for performance monitoring. 1.0 traces 100% of requests, 0.1 traces 10%. For production, start at 0.1-0.2 to manage volume and costs. Use tracesSampler (a function) for dynamic sampling based on transaction name or user context.

captureException sends a full Error object with stack trace — use it in try/catch blocks. captureMessage sends a plain string message without a stack trace — use it for non-exception events like feature flags being hit or important user flows. Both support an optional scope/context object for extra data.

Generally no. Set environment: process.env.NODE_ENV and conditionally initialize only in production/staging. You can use environment configuration in Sentry to route events to different projects per environment. This prevents dev noise from polluting your production error feed.

A release is a version of your code deployed to an environment. When you associate a release with your Sentry config and upload source maps, Sentry can show you which release introduced a regression, mark errors as resolved in a specific version, and display unminified stack traces. Set release to your git commit SHA or semantic version.