Every generated project is connected to Sentry, the platform’s error tracking, from the very beginning. There’s nothing to set up:
- The Sentry DSN is already part of the generated configuration – in the apps’
env/shared.generated.envand in the backend’s deployment configuration. - When an error occurs in app or backend, it automatically appears in your project’s Sentry project – including stack trace and release version.
- This way you see immediately from which release a problem appears, long before users report it.
Where to find your errors
The direct link to your Sentry project is in the platform’s project overview (Sentry tile). How to work there is covered in Working with Sentry.
Tip
Take a quick look at Sentry after every prod release: new errors usually show up there minutes after the deployment.
See also
- Working with Sentry – sign in, read errors, map releases.
- Operations – trace releases and roll back.