diff options
Diffstat (limited to 'doc/operations/error_tracking.md')
| -rw-r--r-- | doc/operations/error_tracking.md | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/doc/operations/error_tracking.md b/doc/operations/error_tracking.md index c3902a560c0..36c5ed03197 100644 --- a/doc/operations/error_tracking.md +++ b/doc/operations/error_tracking.md @@ -4,7 +4,7 @@ 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 --- -# Error Tracking **(FREE)** +# Error Tracking **(FREE ALL)** 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. @@ -82,7 +82,7 @@ You can also review the stack trace. ### Supported language SDKs & Sentry types -In the following table, you can see a list of all event types available through Sentry SDK, and whether they are supported by GitLab Error Tracking. +The following table lists all event types available through Sentry SDK, and whether they are supported by GitLab Error Tracking. | Language | Tested SDK client and version | Endpoint | Supported item types | | -------- | ------------------------------- | ---------- | --------------------------------- | @@ -173,7 +173,7 @@ To enable the Sentry integration: `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. Select **Monitor > Error Tracking**. + 1. Select **Settings > Monitor > Error Tracking**. 1. Under **Enable error tracking**, select the **Active** checkbox. 1. Under **Error tracking backend**, select **Sentry**. 1. Under **Sentry API URL**, enter your Sentry hostname. For example, @@ -201,9 +201,7 @@ to your runner's `config.toml` configuration file, as referenced in If you're asked for the project type while setting up Sentry, select **Go**. -If you see the following error in your GitLab Runner logs, then you should -specify the deprecated -DSN in **Sentry.io > Project Settings > Client Keys (DSN) > Show deprecated DSN**. +To rectify the following error, specify the deprecated DSN in **Sentry.io > Project Settings > Client Keys (DSN) > Show deprecated DSN**. ```plaintext ERROR: Sentry failure builds=0 error=raven: dsn missing private key |