diff options
Diffstat (limited to 'doc/operations/error_tracking.md')
| -rw-r--r-- | doc/operations/error_tracking.md | 18 |
1 files changed, 16 insertions, 2 deletions
diff --git a/doc/operations/error_tracking.md b/doc/operations/error_tracking.md index 36c5ed03197..82982a03016 100644 --- a/doc/operations/error_tracking.md +++ b/doc/operations/error_tracking.md @@ -1,5 +1,5 @@ --- -stage: Analytics +stage: Analyze group: Observability info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- @@ -8,6 +8,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w Error Tracking allows developers to discover and view errors generated by their application. Because error information is surfaced where the code is developed, this increases efficiency and awareness. Users can choose between [GitLab Integrated error tracking](#integrated-error-tracking) and [Sentry based](#sentry-error-tracking) backends. +To leave feedback about Error Tracking bugs or functionality, please comment in the [feedback issue](https://gitlab.com/gitlab-org/opstrace/opstrace/-/issues/2362) or open a [new issue](https://gitlab.com/gitlab-org/opstrace/opstrace/-/issues/new). + ## How error tracking works For error tracking to work, you need: @@ -172,7 +174,7 @@ To enable the Sentry integration: `event:read`, and `event:write` (for resolving events). 1. In GitLab, enable and configure Error Tracking: - 1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. + 1. On the left sidebar, select **Search or go to** and find your project. 1. Select **Settings > Monitor > Error Tracking**. 1. Under **Enable error tracking**, select the **Active** checkbox. 1. Under **Error tracking backend**, select **Sentry**. @@ -206,3 +208,15 @@ To rectify the following error, specify the deprecated DSN in **Sentry.io > Proj ```plaintext ERROR: Sentry failure builds=0 error=raven: dsn missing private key ``` + +## Troubleshooting + +When working with Error Tracking, you might encounter the following issues. + +### Error `Connection failed. Check auth token and try again` + +If the Monitor feature is disabled in the [project settings](../user/project/settings/index.md#configure-project-features-and-permissions), +you might see an error when you try to [enable Sentry integration for a project](#enable-sentry-integration-for-a-project). +The resulting request to `/project/path/-/error_tracking/projects.json?api_host=https:%2F%2Fsentry.example.com%2F&token=<token>` returns a 404 status. + +To fix this issue, enable the Monitor feature for the project. |