| stage | group | info |
|---|---|---|
Monitor |
Platform Insights |
To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments |
Error Tracking helps developers to discover and view errors generated by their application. Because error information is surfaced where the code is developed, error tracking increases efficiency and awareness. Users can choose between GitLab Integrated error tracking and Sentry-based backends.
For error tracking to work, you need:
- Your application configured with the Sentry SDK: When the error happens, Sentry SDK captures information about it and sends it over the network to the backend. The backend stores information about all errors.
- Error tracking backend: The backend can be either GitLab itself or Sentry.
- To use the GitLab backend, see GitLab integrated error tracking. Integrated error tracking is available only on GitLab.com.
- To use Sentry as the backend, see Sentry error tracking. Sentry-based error tracking is available for GitLab.com, GitLab Dedicated, and GitLab self-managed.
The following table gives an overview of the capabilities for each GitLab offering:
| Feature | Availability | Data collection | Data storage | Data query |
|---|---|---|---|---|
| GitLab integrated Error Tracking | GitLab.com | With Sentry SDK | On GitLab.com | With GitLab.com |
| Sentry-based Error Tracking | GitLab.com, GitLab Dedicated, GitLab self-managed | With Sentry SDK | On Sentry instance (Cloud Sentry.io or self-hosted Sentry) | With GitLab.com or Sentry instance |