5 solution docs
Sentry solution docs
Stack traces with the release and route attached, scrubbed of user data first.
Pick Sentry and all 5 land in docs/solutions/sentry/, next to the rules and skills that reference them.
Every Sentry doc in the registry
Tags: beforeSend · bots · cost · deployment · fingerprints · gdpr · grouping · incident-response · noise · performance · pii · privacy · releases · sampling · security · sentry · source-maps · tracing · triage · vercel
One issue with 40,000 events: grouping, fingerprints and the helper that ruined them
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.
sentry · fingerprints · grouping · triage
Scrubbing PII before it leaves your process, not after it reaches Sentry
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.
sentry · pii · privacy · gdpr
Source maps on Vercel: why your production stack traces are unreadable
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.
sentry · source-maps · vercel · deployment
Telling a real incident from a bot, a browser extension or a stale tab
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.
sentry · triage · noise · bots
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.
sentry · tracing · performance · cost