Sentry Architecture Variants

Prerequisites

• Application architecture documented

• Service inventory available

• Team ownership defined

• Deployment model understood

Instructions

• Identify application type (monolith, microservices, serverless, hybrid)

• For monoliths, create single project and use tags for module filtering

• For microservices, create one project per service with shared config

• Configure distributed tracing with sentry-trace and baggage headers

• For serverless, use framework-specific SDK wrappers

• Set up cross-system tracing for hybrid architectures

• Configure message queue integration with trace context propagation

• Add tenant isolation tags for multi-tenant applications

• Set up edge function monitoring with platform-specific SDKs

• Document architecture decisions and implement team-based access controls

Output

• Architecture-appropriate Sentry configuration

• Project structure matching application topology

• Distributed tracing configured

• Team-based access controls

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 Architecture Guide

• Distributed Tracing

Overview

Execute sentry architecture patterns for different application types.