sentry-reference-architecture

Best-practice Sentry architecture patterns.Use when designing Sentry integration architecture,structuring projects, or planning enterprise rollout.Trigger with phrases like "sentry architecture", "sentry best practices","design sentry integration", "sentry project structure".

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

When & Why to Use This Skill

The Sentry Reference Architecture skill provides a comprehensive framework for designing and implementing industry-standard error tracking and performance monitoring. It streamlines the process of structuring Sentry projects, configuring distributed tracing, and establishing efficient alert hierarchies, ensuring high visibility into application health and faster incident resolution for enterprise-grade deployments.

Use Cases

  • 1. Enterprise Rollout Planning: Designing a scalable Sentry organization and team structure to support large-scale software ecosystems.
  • 2. Microservices Observability: Configuring distributed tracing and header propagation to track errors and performance bottlenecks across complex service meshes.
  • 3. Standardizing Error Handling: Implementing global middleware and domain-specific error classes to ensure consistent data capture and debugging context.
  • 4. Alert Fatigue Reduction: Establishing sophisticated alert hierarchies and routing rules based on team ownership and issue severity to optimize incident response.
namesentry-reference-architecture
description|
allowed-toolsRead, Write, Edit, Grep
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Sentry Reference Architecture

Prerequisites

  • Sentry organization created
  • Team structure defined
  • Service inventory documented
  • Alert escalation paths established

Instructions

  1. Define project structure based on application architecture
  2. Create centralized SDK configuration module with standard settings
  3. Implement global error handler middleware with Sentry integration
  4. Create domain-specific error classes with appropriate tags
  5. Configure distributed tracing with header propagation between services
  6. Set up alert hierarchy (critical, warning, info) with routing rules
  7. Configure issue routing based on team ownership and tags
  8. Enable release tracking for every deployment
  9. Document architecture patterns and configuration standards
  10. 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.

Resources