sentry-multi-env-setup

Configure Sentry across multiple environments.Use when setting up Sentry for dev/staging/production,managing environment-specific configurations, or isolating data.Trigger with phrases like "sentry environments", "sentry staging setup","multi-environment sentry", "sentry dev vs prod".

⭐878stars🔀101forks📁View on GitHub🕐Updated Jan 4, 2026

When & Why to Use This Skill

This Claude skill automates the professional configuration of Sentry across multiple deployment environments such as development, staging, and production. It streamlines the implementation of environment-specific DSNs, optimized sample rates, and intelligent alert routing to ensure robust error tracking and data isolation for modern software development workflows.

Use Cases

  • New Project Initialization: Quickly establish a standardized Sentry setup for new applications requiring distinct configurations for dev, staging, and production environments.
  • Performance & Quota Management: Automatically configure environment-specific sample rates (e.g., 100% in dev for debugging vs. 10% in prod for performance) to manage Sentry event quotas effectively.
  • Intelligent Alerting Workflows: Create production-only alert rules and lower-priority staging notifications to ensure critical production issues are prioritized while maintaining a clean developer feedback loop.
  • Data Integrity & Isolation: Implement conditional DSN loading and environment tagging to prevent local development or testing data from polluting production error analytics and dashboards.
namesentry-multi-env-setup
description|
allowed-toolsRead, Write, Edit, Grep
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Sentry Multi Env Setup

Prerequisites

  • Environment naming convention defined
  • DSN management strategy
  • Sample rate requirements per environment
  • Alert routing per environment

Instructions

  1. Set environment option in SDK init to match deployment target
  2. Configure environment-specific sample rates (100% dev, 10% prod)
  3. Choose project structure (single with environments vs separate projects)
  4. Set up separate DSNs per environment in environment variables
  5. Implement conditional DSN loading to disable in development
  6. Add environment context and tags in beforeSend hook
  7. Configure environment filters in Sentry dashboard
  8. Create production-only alert rules with appropriate conditions
  9. Set up lower-priority staging alerts for development feedback
  10. Document environment configuration and best practices for team

Output

  • Environment-specific Sentry configuration
  • Separate or shared projects configured
  • Environment-based alert rules
  • Sample rates optimized per environment

Error Handling

See {baseDir}/references/errors.md for comprehensive error handling.

Examples

See {baseDir}/references/examples.md for detailed examples.

Resources