Frontend (@sentry/vue, loaded via build-time-gated dynamic import — no
VITE_SENTRY_DSN_FRONTEND, no Sentry in the bundle; init joins the mount
gate so instrumentation precedes the first render):
- uncaught errors, route-change tracing / Web Vitals, error-only masked
Session Replay, console.error capture fingerprinted per message prefix
so each fallback source stays a distinct issue
- explicit ip-source:exhausted signal via the app-events bus
- hidden source maps uploaded (then deleted) by @sentry/vite-plugin,
gated on SENTRY_AUTH_TOKEN
Backend (@sentry/node, bootstrapped by sentry-instrument.js via
node --import so ESM loader hooks land before express; never loaded
without SENTRY_DSN_BACKEND):
- Express error capture + per-route tracing
- logger hook mirrors warn+ lines to Sentry Logs and elevates error+
to grouped, alertable Issues
- Sentry Crons check-ins for the MaxMind / CAIDA / service-status jobs
via the no-op-without-DSN wrapper common/sentry-cron.js
Delivery & ops:
- first-party tunnel /api/monitoring relays envelopes past ad blockers;
DSN-allowlisted (never an open relay), exempt from the shared rate
limiter with its own generous ceiling
- rate-limit ledger file becomes opt-in now that the warn line reaches
Sentry Logs; ecosystem.config.cjs carries the --import flag for pm2
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jason5ng32andClaude Fable 5.1