sentry-advanced-troubleshooting

# Sentry Advanced Troubleshooting ## Overview This skill addresses complex Sentry issues that go beyond basic setup: events that silently drop, source maps that refuse to resolve, distributed traces with gaps between services, SDK memory leaks, conflicts with other observability libraries, and network-level DSN blocking. Each section provides a systematic diagnosis path with concrete commands and code to identify root causes. ## Prerequisites - Sentry SDK v8 installed and initialized (see `sentry-install-auth` skill) - Access to application logs, Sentry dashboard, and project settings - Sentry CLI installed (`npm install -g @sentry/cli`) for source map debugging - Network diagnostic tools available (curl, dig) - `debug: true` enabled in SDK init for verbose console output during troubleshooting ## Instructions ### Step 1 — Diagnose Silently Dropped Events Events can vanish at multiple points between your code and the Sentry dashboard. Work through each layer systematically. **Enable debug mode to see SDK internals:** ```typescript import * as Sentry from '@sentry/node'; Sentry.init({ dsn: process.env.SENTRY_DSN, debug: true, // Prints all SDK decisions to console // Wrap transport to log every outbound envelope transport: (options) => { const transport = Sentry.makeNodeTransport(options); return { ...transport, send: async (envelope) => { const [header, items] = envelope; console.log('[Sentry Transport] Outbound envelope:'...