Sentry Monitoring

The default Sentry setup catches exceptions but ships at 100% sample rate, leaks PII, doesn't connect releases, and floods you with noise. This skill is the cleaned-up version.

When to use

• New app — wire Sentry from day 1.
• Existing Sentry account that has become useless from noise.
• Adding performance monitoring on top of error monitoring.
• Setting up release tracking so you know which deploy broke things.

When NOT to use

• High-throughput data plane (>100k errors/min) — Sentry's pricing curves up; consider Honeycomb or self-hosted.
• You're already deep on Datadog APM with error tracking — less value-add.

Setup (Next.js)