sentry-reference-architecture
Manage 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".
Install
mkdir -p .claude/skills/sentry-reference-architecture && curl -L -o skill.zip "https://mcp.directory/api/skills/download/9037" && unzip -o skill.zip -d .claude/skills/sentry-reference-architecture && rm skill.zipInstalls to .claude/skills/sentry-reference-architecture
About this skill
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 (Business plan+ for team features)
@sentry/nodev8+ 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
Create lib/sentry.ts imported by every service to enforce org-wide defaults:
// lib/sentry.ts
import * as Sentry from '@sentry/node';
import { nodeProfilingIntegration } from '@sentry/profiling-node';
export interface SentryServiceConfig {
serviceName: string;
dsn: string;
environment?: string;
version?: string;
tracesSampleRate?: number;
ignoredTransactions?: string[];
}
export function initSentry(config: SentryServiceConfig): void {
const env = config.environment || process.env.NODE_ENV || 'development';
Sentry.init({
dsn: config.dsn,
environment: env,
release: `${config.serviceName}@${config.version || 'unknown'}`,
serverName: config.serviceName,
tracesSampleRate: config.tracesSampleRate ?? (env === 'production' ? 0.1 : 1.0),
sendDefaultPii: false,
maxBreadcrumbs: 50,
integrations: [nodeProfilingIntegration()],
ignoreErrors: [
'ResizeObserver loop completed with undelivered notifications',
/Loading chunk \d+ failed/,
'AbortError',
],
tracesSampler: ({ name, parentSampled }) => {
if (parentSampled !== undefined) return parentSampled;
const ignored = config.ignoredTransactions || [
'GET /health', 'GET /healthz', 'GET /ready', 'GET /metrics',
];
if (ignored.some(p => name.includes(p))) return 0;
return config.tracesSampleRate ?? (env === 'production' ? 0.1 : 1.0);
},
beforeSend(event) {
if (event.request?.headers) {
delete event.request.headers['authorization'];
delete event.request.headers['cookie'];
delete event.request.headers['x-api-key'];
}
return event;
},
initialScope: {
tags: { service: config.serviceName, team: process.env.TEAM_NAME || 'unassigned' },
},
});
}
export { Sentry };
Bootstrap in each service:
import { initSentry } from '@acme/sentry-config';
initSentry({ serviceName: 'api-gateway', dsn: process.env.SENTRY_DSN! });
// Must run BEFORE other imports that need instrumentation
Step 3 — Error Handling Middleware
Express:
// lib/sentry-middleware.ts
import * as Sentry from '@sentry/node';
import type { Request, Response, NextFunction, ErrorRequestHandler } from 'express';
export function sentryRequestHandler() {
return (req: Request, _res: Response, next: NextFunction): void => {
Sentry.setTag('http.route', req.route?.path || req.path);
if (req.user) Sentry.setUser({ id: req.user.id });
next();
};
}
export const sentryErrorHandler: ErrorRequestHandler = (err, req, res, _next) => {
const status = (err as any).statusCode || 500;
Sentry.withScope((scope) => {
scope.setLevel(status >= 500 ? 'error' : 'warning');
scope.setTag('http.status_code', String(status));
scope.setContext('request', { method: req.method, url: req.originalUrl });
status >= 500 ? Sentry.captureException(err) : Sentry.captureMessage(err.message, 'warning');
});
res.status(status).json({ error: status >= 500 ? 'Internal server error' : err.message });
};
// Wire: app.use(sentryRequestHandler()) → routes → app.use(sentryErrorHandler)
FastAPI (Python):
import sentry_sdk, os
from sentry_sdk.integrations.fastapi import FastApiIntegration
def init_sentry(service_name: str) -> None:
sentry_sdk.init(
dsn=os.environ["SENTRY_DSN"],
environment=os.getenv("ENV", "development"),
release=f"{service_name}@{os.getenv('SERVICE_VERSION', 'unknown')}",
traces_sample_rate=0.1,
send_default_pii=False,
integrations=[FastApiIntegration(transaction_style="endpoint")],
before_send=lambda event, hint: _scrub(event),
)
def _scrub(event):
headers = event.get("request", {}).get("headers", {})
for k in ["authorization", "cookie", "x-api-key"]:
headers.pop(k, None)
return event
Step 4 — Distributed Tracing
HTTP (automatic): SDK v8 auto-propagates sentry-trace + baggage headers on fetch/http. All services in the same org link automatically.
Message queues (manual propagation):
// lib/sentry-queue.ts
import * as Sentry from '@sentry/node';
export function publishWithTrace<T>(queue: string, payload: T, publish: Function) {
return Sentry.startSpan({ name: `queue.publish.${queue}`, op: 'queue.publish' }, async () => {
const headers: Record<string, string> = {};
const span = Sentry.getActiveSpan();
if (span) {
headers['sentry-trace'] = Sentry.spanToTraceHeader(span);
headers['baggage'] = Sentry.spanToBaggageHeader(span) || '';
}
await publish(queue, { payload, headers });
});
}
export function consumeWithTrace<T>(queue: string, msg: { payload: T; headers: Record<string, string> }, handler: (p: T) => Promise<void>) {
return Sentry.continueTrace(
{ sentryTrace: msg.headers['sentry-trace'], baggage: msg.headers['baggage'] },
() => Sentry.startSpan({ name: `queue.process.${queue}`, op: 'queue.process' }, () => handler(msg.payload))
);
}
Step 5 — Team-Based Alert Routing
Configure in Project Settings > Ownership Rules:
# .sentry/ownership-rules
path:src/payments/** #payments-team
path:src/auth/** #platform-team
url:*/api/v1/payments/* #payments-team
tags.service:payment-api #payments-team
* #platform-team
Alert tiers:
- P0 Critical: error rate > 50/min OR crash-free < 95% — PagerDuty on-call, 15 min SLA
- P1 Warning: new production issue or regression — Slack #alerts-prod, same-day SLA
- P2 Performance: P95 > 2s or Apdex < 0.7 — Slack #alerts-perf, next sprint
- P3 Info: new staging issue — Slack #alerts-staging, backlog triage
Step 6 — Source Map Uploads (Monorepo)
#!/usr/bin/env bash
# scripts/upload-sourcemaps.sh — run in CI after build
set -euo pipefail
SERVICE="${1:?Usage: upload-sourcemaps.sh <service>}"
RELEASE="${SERVICE}@$(git rev-parse --short HEAD)"
npx @sentry/cli releases new "$RELEASE" --org "$SENTRY_ORG" --project "$SERVICE"
npx @sentry/cli sourcemaps upload --org "$SENTRY_ORG" --project "$SERVICE" \
--release "$RELEASE" --url-prefix "~/" --validate "./services/${SERVICE}/dist/"
npx @sentry/cli releases set-commits "$RELEASE" --org "$SENTRY_ORG" --auto
npx @sentry/cli releases finalize "$RELEASE" --org "$SENTRY_ORG"
Webpack plugin alternative (auto-uploads on build):
import { sentryWebpackPlugin } from '@sentry/webpack-plugin';
export default {
devtool: 'source-map',
plugins: [sentryWebpackPlugin({
org: process.env.SENTRY_ORG,
project: 'web-app',
authToken: process.env.SENTRY_AUTH_TOKEN,
sourcemaps: { filesToDeleteAfterUpload: ['./dist/**/*.map'] },
})],
};
Step 7 — Custom Integrations
Wrap internal SDK calls with spans for tracing visibility:
import * as Sentry from '@sentry/node';
export function withSpan<T>(op: string, desc: string, fn: () => Promise<T>, attrs?: Record<string, string | number>): Promise<T> {
return Sentry.startSpan({ name: desc, op, attributes: attrs }, async (span) => {
try { const r = await fn(); span.setStatus({ code: 1, message: 'ok' }); return r; }
catch (e) { span.setStatus({ code: 2, message: String(e) }); throw e; }
});
}
// Usage: await withSpan('payment.charge', 'charge $50', () => gateway.charge(5000, 'usd', custId));
Step 8 — SentryService Wrapper
Production wrapper with singleton, metrics, and graceful shutdown:
// lib/sentry-service.ts
import * as Sentry from '@sentry/node';
export class SentryService {
private static instance: SentryService | null = null;
private initialized = false;
private constructor(private config: { serviceName: string; dsn: string; version?: string }) {}
static getInstance(config?: { serviceName: string; dsn: string; version?: string }): SentryService {
if (!SentryService.instance) {
if (!config) throw new Error('Config required on first call');
SentryService.instance = new SentryService(config);
}
return SentryService.instance;
}
init(): void {
if (this.initialized) return;
const { initSentry } = require('./sentry');
initSentry(this.config);
this.initialized = true;
}
captureError(error: Error, ctx?: { tags?: Record<string, string>; extra?: Record<string, unknown>; level?: Sentry.SeverityLevel }): string {
return Sentry.withScope((scope) => {
if (ctx?.tags) Object.entries(ctx.tags
---
*Content truncated.*
More by jeremylongshore
View all skills by jeremylongshore →You might also like
flutter-development
aj-geddes
Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.
drawio-diagrams-enhanced
jgtolentino
Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.
ui-ux-pro-max
nextlevelbuilder
"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
nano-banana-pro
garg-aayush
Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.
pdf-to-markdown
aliceisjustplaying
Convert entire PDF documents to clean, structured Markdown for full context loading. Use this skill when the user wants to extract ALL text from a PDF into context (not grep/search), when discussing or analyzing PDF content in full, when the user mentions "load the whole PDF", "bring the PDF into context", "read the entire PDF", or when partial extraction/grepping would miss important context. This is the preferred method for PDF text extraction over page-by-page or grep approaches.
Related MCP Servers
Browse all serversBy Sentry. MCP server and CLI that provides tools for AI agents working on iOS and macOS Xcode projects. Build, test, li
Context Portal: Manage project memory with a database-backed system for decisions, tracking, and semantic search via a k
Claude Historian is a free AI search engine offering advanced search, file context, and solution discovery in Claude Cod
Claude Historian: AI-powered search for Claude Code conversations—find files, errors, context, and sessions via JSONL pa
Sketch Context connects Sketch design files to dev workflows, enabling easy component extraction and real-time design wi
Integrate with Podman for seamless container creation, management, and orchestration in automated DevOps and microservic
Stay ahead of the MCP ecosystem
Get weekly updates on new skills and servers.