sentry-reference-architecture

Featured

Design production-grade Sentry architecture for multi-service organizations. Use when planning Sentry rollout, structuring projects across teams, building shared config modules, or setting up distributed tracing. Trigger: "sentry architecture", "sentry project structure", "sentry reference design", "sentry distributed tracing".

AI & Automation 2,926 stars 433 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Sentry Reference Architecture ## Overview Enterprise Sentry architecture patterns for multi-service organizations. Covers centralized configuration, project topology, team-based alert routing, distributed tracing, error middleware, source map management, and a production-ready SentryService wrapper. ## Prerequisites - Sentry organization at [sentry.io](https://sentry.io) (Business plan+ for team features) - `@sentry/node` v8+ installed (`npm install @sentry/node @sentry/profiling-node`) - Service inventory and team ownership documented - Node.js 18+ (ESM and native fetch instrumentation) ## Instructions ### Step 1 — Project Structure Strategy **Pattern A: One Project Per Service (3+ services, recommended)** ``` Organization: acme-corp ├── Team: platform-eng │ ├── Project: api-gateway (Node/Express) │ ├── Project: auth-service (Node/Fastify) │ └── Project: user-service (Node/Express) ├── Team: payments │ ├── Project: payment-api (Node/Express) │ └── Project: billing-worker (Node worker) └── Team: frontend ├── Project: web-app (React/Next.js) └── Project: mobile-app (React Native) ``` Benefits: independent quotas, team-scoped alerts, per-service rate limits, isolated release tracking. **Pattern B: Shared Project (< 3 services, single team)** — one project with `Environment` tags (production/staging/dev). Simpler setup; outgrow when alert noise exceeds one team. ### Step 2 — Centralized Config Module Creat...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
1 years ago
Last Updated
yesterday
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Featured

sentry-architecture-variants

Configure Sentry error tracking and performance monitoring for different application architectures. Use when setting up Sentry for monoliths, microservices, serverless functions, event-driven systems, frontend SPAs, mobile apps, or hybrid deployments. Trigger: "sentry monolith setup", "sentry microservices tracing", "sentry serverless lambda", "sentry event-driven kafka", "sentry react native", "sentry architecture pattern".

2,926 Updated yesterday
jeremylongshore
AI & Automation Featured

sentry-policy-guardrails

Enforce organizational governance and policy guardrails for Sentry usage. Use when standardizing Sentry configuration across services, enforcing PII scrubbing, building shared config packages, or auditing drift. Trigger with phrases like "sentry governance", "sentry policy", "sentry standards", "enforce sentry config", "sentry compliance".

2,926 Updated yesterday
jeremylongshore
AI & Automation Featured

sentry-multi-env-setup

Configure Sentry across development, staging, and production environments with separate DSNs, environment-specific sample rates, per-environment alert rules, and dashboard filtering. Use when setting up Sentry for dev/staging/production, managing environment-specific configurations, isolating data between environments, or configuring .env files for per-environment DSNs. Trigger: "sentry environments", "sentry staging setup", "multi-environment sentry", "sentry dev vs prod", "sentry DSN per env".

2,926 Updated yesterday
jeremylongshore