Sentry Multi Env Setup
Prerequisites
-
Environment naming convention defined
-
DSN management strategy
-
Sample rate requirements per environment
-
Alert routing per environment
Instructions
-
Set environment option in SDK init to match deployment target
-
Configure environment-specific sample rates (100% dev, 10% prod)
-
Choose project structure (single with environments vs separate projects)
-
Set up separate DSNs per environment in environment variables
-
Implement conditional DSN loading to disable in development
-
Add environment context and tags in beforeSend hook
-
Configure environment filters in Sentry dashboard
-
Create production-only alert rules with appropriate conditions
-
Set up lower-priority staging alerts for development feedback
-
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 ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error handling.
Examples
See ${CLAUDE_SKILL_DIR}/references/examples.md for detailed examples.
Resources
-
Sentry Environments
-
Filtering Events
Overview
Configure Sentry across multiple environments.