sentry-observability

# Sentry Observability Integration ## Overview Wire Sentry into your logging, metrics, APM, and dashboard toolchain so every error carries full context and every metric correlates back to root-cause events. This skill covers three integration layers: structured logging (winston, pino, structlog) with Sentry event ID correlation, business metrics with error-rate tracking, and cross-tool linking via Sentry Discover, Grafana webhooks, and APM tools. See also: [Logging integration details](references/logging-integration.md) | [Metrics patterns](references/metrics-integration.md) | [APM tool cross-linking](references/apm-tool-integration.md) ## Prerequisites - Sentry SDK v8+ installed (`@sentry/node` for Node.js, `sentry-sdk` for Python) - At least one structured logger configured (winston, pino, or structlog) - Sentry project DSN available in environment (`SENTRY_DSN`) - Dashboard platform accessible (Sentry Discover, Grafana, or Datadog) - Alert routing strategy decided (who gets paged, where warnings go) ## Instructions ### Step 1 — Attach Sentry Event IDs to Structured Logs The core pattern: every log line that triggers a Sentry event carries the event ID, and every Sentry event carries the log context. This creates a two-way link between your log aggregator and Sentry. **Winston (Node.js) — custom transport:** ```typescript import winston from 'winston'; import * as Sentry from '@sentry/node'; class SentryTransport extends winston.Transport { log(info: any, callb...