OpenParable
Skip to content
← Back to skills

Sentry Multi Env Setup

DevOps & Security
sentry-multi-env-setup

Sentry Multi Env Setup is an Agent Skill for devops & security published in the Dicklesworthstone/pi_agent_rust repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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".

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Dicklesworthstone/pi_agent_rust/blob/HEAD/tests/ext_conformance/artifacts/plugins-community/plugins/saas-packs/sentry-pack/skills/sentry-multi-env-setup/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/sentry-multi-env-setup, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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