blob: cf50e1b2f916610f2bfbea811866b9aa4e6b818a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
# Error Tracking
> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/169) in GitLab 11.8.
Error tracking provides a way to ingest and display errors from your managed servers directly in GitLab.
## Sentry error tracking
[Sentry](https://sentry.io/) is an open source error tracking system. GitLab allows administrators to integrate Sentry with GitLab, to allow users to view a list of Sentry errors in GitLab itself.
### Deploying Sentry
You may sign up to the cloud hosted https://sentry.io or deploy your own on-premise instance.
On-premise deployment instructions are detailed in the [Sentry docs](https://docs.sentry.io/server/installation/).
### Enabling Sentry
GitLab provides an easy way to connect to your Sentry instance from within your project.
1. Sign up to Sentry.io or [deploy your own](#deploying-sentry) Sentry instance
1. [Find or generate](https://docs.sentry.io/api/auth/) a Sentry auth token for your Sentry project
1. Navigate to your project’s **Settings > Operations** and provide the Sentry API URL and auth token
1. Ensure that the 'Active` checkbox is set
1. Click **Save changes** for the changes to take effect.
1. You can now visit **Operations > Error Tracking** in your project's sidebar to [view a list](#error-tracking-list) of Sentry errors
## Error Tracking List
The Error Tracking list may be found at **Operations > Error Tracking** in your project's sidebar.
|
