Error tracking runs through Sentry. New organizations connect their own Sentry account under Connections (OAuth or API token). Then enable Sentry per app, homepage, or backend under Features.
Typical flow
- Connect Sentry under Connections (cloud or custom instance).
- In the project editor, enable Sentry for the app / homepage / backend and select the connection.
- On save, the platform creates the Sentry project and writes the DSN into the generated configuration (
env/*.generated.envor GitOpsgenerated.yaml).
When an error occurs in the app or backend, it lands in the connected Sentry project – including stack trace and release version.
Note
Without a linked Sentry connection, error tracking stays disabled. Platform-hosted Sentry remains only for the platform operator.
Where to find your errors
The link to the Sentry project is on the project overview (Sentry tile) when Sentry is enabled for the component. Details: Working with Sentry.
See also
- Sentry: Credentials – add a token or OAuth connection
- Connections – add a Sentry account
- Working with Sentry – reading issues and mapping releases
- Operations – tracing and rolling back releases