Sentry integration: error monitoring, releases, and performance

FeatureShipped· by Elsama· 2 months ago

Wire up Sentry on both the Next.js front-end and the Node/Edge server side. Capture client errors with source maps, server runtime errors, slow API spans, and Web Vitals. Tag every event with org_id and project_id so support can filter by tenant. Tie commits to releases via the Sentry CLI in deploy/deploy.sh, enable Cron monitoring for scheduled jobs (digest emails, AI background jobs), and add a Report this link in the global error boundary. Optional PR comments for new errors introduced by a change.

Comments (1)

Elsama· 2 months ago
PR ready: https://github.com/El-SaMa/hollahoop/pull/22

Implemented Sentry wiring for Next.js client/server/request errors, a global error boundary, tenant tags, source map/release config, and deploy release tracking.

Owner action before full production capture: create the Sentry project and set SENTRY_DSN, NEXT_PUBLIC_SENTRY_DSN, SENTRY_ORG, SENTRY_PROJECT, and SENTRY_AUTH_TOKEN in the production env.

Join the discussion