Sentry Policy Guardrails

Prerequisites

• Organization-wide standards documented

• Team structure defined

• Compliance requirements identified

• Shared configuration package repository

Instructions

• Create shared Sentry configuration package with organization defaults

• Define enforced settings that cannot be overridden (sendDefaultPii, sample rates)

• Implement mandatory PII scrubbing in beforeSend hook

• Add environment enforcement to block test data in production

• Create standard alert policy templates with required rules

• Implement project naming validation following team-service-environment pattern

• Build configuration audit script to check compliance across projects

• Set up compliance dashboard with metrics reporting

• Document policy requirements and share with all teams

• Enforce shared config package usage in CI/CD pipelines

Output

• Shared Sentry configuration package

• Enforced organization defaults

• Alert policy templates

• Project naming validation

• Compliance audit reports

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 Organization Settings

• Sentry API

Overview

Implement governance and policy guardrails for Sentry.