Sentry Reference Architecture
Prerequisites
- •Sentry organization created
- •Team structure defined
- •Service inventory documented
- •Alert escalation paths established
Instructions
- •Define project structure based on application architecture
- •Create centralized SDK configuration module with standard settings
- •Implement global error handler middleware with Sentry integration
- •Create domain-specific error classes with appropriate tags
- •Configure distributed tracing with header propagation between services
- •Set up alert hierarchy (critical, warning, info) with routing rules
- •Configure issue routing based on team ownership and tags
- •Enable release tracking for every deployment
- •Document architecture patterns and configuration standards
- •Review and adjust based on error patterns after initial deployment
Output
- •Project structure following best practices
- •Centralized SDK configuration module
- •Distributed tracing configured across services
- •Alert routing rules defined
Error Handling
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.