# Sentry solution docs

- [One issue with 40,000 events: grouping, fingerprints and the helper that ruined them](https://agenticboilerplate.com/cookbook/sentry/grouping-noisy-errors-with-fingerprints): Sentry groups by stack trace, so a shared fetch wrapper merges every unrelated failure into one useless issue. Fingerprints put the grouping back where the cause is.
- [Scrubbing PII before it leaves your process, not after it reaches Sentry](https://agenticboilerplate.com/cookbook/sentry/scrubbing-pii-before-it-leaves-the-process): Server-side scrubbing runs after the data has crossed the network. beforeSend runs in your process, and it is the only layer you fully control.
- [Source maps on Vercel: why your production stack traces are unreadable](https://agenticboilerplate.com/cookbook/sentry/source-maps-on-vercel): A minified trace means the build never uploaded source maps. The auth token, the release name and the preview environment are the three things that are usually wrong.
- [Telling a real incident from a bot, a browser extension or a stale tab](https://agenticboilerplate.com/cookbook/sentry/telling-a-real-incident-from-a-bot): Most of a new project's error feed is not your bug. The four signatures of noise, how to filter each one at the right layer, and the three signals that mean it is real.
- [Trace sample rates that do not bankrupt you](https://agenticboilerplate.com/cookbook/sentry/trace-sample-rates-that-do-not-bankrupt-you): Errors are cheap and spans are not. How to pick tracesSampleRate, why the edge runtime needs a lower one, and how to keep the traces you actually need while dropping 95% of the rest.

---

Agentic Boilerplate: A Next.js repo your agent already knows. Free during launch, then $99 once.

- Site map for agents: https://agenticboilerplate.com/llms.txt
- Public API: https://agenticboilerplate.com/openapi.json
- Contact: agenticstudio@gmail.com