Production checklist
Sentry production checklist: 5 checks before launch
5 checks for running Sentry in production: 1 should-do and 4 good-to-haves. Each one says why it matters, how to verify it and where the docs are.
Updated . Every check links the vendor’s own docs.
Should do (1)
Scrub personal data before events leave your app
Error payloads often contain emails, tokens and request bodies.
Check the config
sendDefaultPii stays false (the default) in Sentry.init, and the project’s Security & Privacy settings have data scrubbing on. Check a recent event: no emails, tokens or request bodies.
Sentry.init({ dsn: "<dsn>", sendDefaultPii: false });
Good to have (4)
Set trace and replay sample rates for production
A 100% sample rate gets expensive fast and adds overhead.
Check the config
Production uses sample rates below 1.0.
Sentry.init({ tracesSampleRate: 0.1, replaysSessionSampleRate: 0.1 });Upload source maps to Sentry without serving them publicly
Public source maps hand anyone your original source code.
Verify with a request
Fetching a .map file from your production site should return 404, while Sentry stack traces still show your original source.
curl -s -o /dev/null -w "%{http_code}\n" https://<your-app>/<path-to-a-bundle>.js.mapAlert on new issues and error spikes
Errors nobody hears about aren’t monitoring.
How to verify
Under Alerts, at least one issue alert sends new issues and spikes to email, Slack or your pager.
Tag events with environment and release
Lets you tell production errors from previews and see which deploy introduced a bug.
Check the config
Sentry.init sets environment and release, and the Issues page lets you filter production errors by release.
Sentry.init({ environment: "production", release: "<git sha>" });
Get the checklist for your whole stack
Design your stack or map your repo in StackPrism, and the Improve panel lists the checks for every technology on it and keeps track of what you’ve done. Building with an AI app builder? Start with the vibe coding checklist.