## Motivation We intend to update the GitLab error UI to use the GitLab Observability UI. This will eventually enable users to access errors, and other observability data such as metrics, traces, and logs all from the same database and visualization tool. As such, our aim is not to reach feature parity relative to Sentry, but to enable users to tie together errors, with observability data and with other parts of GitLab such as issues, merge requests, and more. For users requiring the full Sentry feature set, users can connect to their existing Sentry backend to the GitLab Observability UI as a datasource. ## Acceptance criteria `Error Tracking` page built using the GitLab Observability UI * On by default. * Shows a plain list of errors for the project, sorted by occurrence. * Uses an external Error Tracking data source (cloud or self-hosted Sentry) **Owner**: @drosse