When an error occurs in an app, homepage, or backend, it lands in the associated Sentry project with the stack trace and the release version. That shows you whether an error is new, how often it happens, and with which version it started.
The platform no longer runs a Sentry of its own. Error tracking goes through the Sentry account you connect under Connections, either Sentry Cloud or a self-hosted instance; without a Sentry connection, it stays disabled.
Enabling error tracking
- Connect your Sentry account under Connections with Connect with Sentry for Sentry Cloud or with an API token, which also works for your own instance. Sentry: credentials lists the scopes the token needs.
- In the project editor, open the app, the homepage, or the backend, enable the Sentry option under Features, and select the connection.
- Choose the Sentry project: automatic creation, where the platform derives the slug from project and component, an existing project in your Sentry organization, or a new project with a slug of your choice.
- Save. The platform creates the Sentry project or links the one you selected, and writes the DSN to which the application sends its errors into the generated configuration.
Each component can have its own Sentry project; an app, its homepage, and its backend then appear as separate projects in your Sentry organization.
Viewing errors
When Sentry is enabled for a component, the Sentry tile in the project overview leads directly to the project in your Sentry organization. Working with Sentry describes how to read issues there.