2020-10-01 14:10:20 -04:00
---
stage: Monitor
group: Health
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
---
2020-10-05 20:09:01 -04:00
# Alert integrations
2020-10-01 14:10:20 -04:00
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/13203) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 12.4.
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/42640) to [GitLab Core](https://about.gitlab.com/pricing/) in 12.8.
2020-11-12 13:09:26 -05:00
GitLab can accept alerts from any source via a webhook receiver. This can be configured
generically or, in GitLab versions 13.1 and greater, you can configure
2020-10-01 14:10:20 -04:00
[External Prometheus instances ](../metrics/alerts.md#external-prometheus-instances )
to use this endpoint.
2020-10-15 20:08:56 -04:00
## Integrations list
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/245331) in [GitLab Core](https://about.gitlab.com/pricing/) 13.5.
With Maintainer or higher [permissions ](../../user/permissions.md ), you can view
the list of configured alerts integrations by navigating to
**Settings > Operations** in your project's sidebar menu, and expanding **Alerts** section.
The list displays the integration name, type, and status (enabled or disabled):
![Current Integrations ](img/integrations_list_v13_5.png )
2020-10-05 20:09:01 -04:00
## Configuration
2020-11-12 13:09:26 -05:00
GitLab can receive alerts via a [HTTP endpoint ](#generic-http-endpoint ) that you configure,
or the [Prometheus integration ](#external-prometheus-integration ).
2020-10-08 14:08:32 -04:00
2020-11-12 13:09:26 -05:00
### Generic HTTP Endpoint **CORE**
2020-10-01 14:10:20 -04:00
2020-11-12 13:09:26 -05:00
Enabling the Generic HTTP Endpoint activates a unique HTTP endpoint that can
receive alert payloads in JSON format. You can always
[customize the payload ](#customize-the-alert-payload-outside-of-gitlab ) to your liking.
2020-10-01 14:10:20 -04:00
1. Sign in to GitLab as a user with maintainer [permissions ](../../user/permissions.md )
for a project.
2020-10-05 20:09:01 -04:00
1. Navigate to **Settings > Operations** in your project.
1. Expand the **Alerts** section, and in the **Integration** dropdown menu, select **Generic** .
2020-10-01 14:10:20 -04:00
1. Toggle the **Active** alert setting to display the **URL** and **Authorization Key**
for the webhook configuration.
2020-11-12 13:09:26 -05:00
### HTTP Endpoints **PREMIUM**
> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4442) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.6.
In [GitLab Premium ](https://about.gitlab.com/pricing/ ), you can create multiple
unique HTTP endpoints to receive alerts from any external source in JSON format,
and you can [customize the payload ](#customize-the-alert-payload-outside-of-gitlab ).
1. Sign in to GitLab as a user with maintainer [permissions ](../../user/permissions.md )
for a project.
1. Navigate to **Settings > Operations** in your project.
1. Expand the **Alerts** section.
1. For each endpoint you want to create:
1. In the **Integration** dropdown menu, select **HTTP Endpoint** .
1. Name the integration.
1. Toggle the **Active** alert setting to display the **URL** and **Authorization Key**
2020-11-18 10:09:08 -05:00
for the webhook configuration. You must also input the URL and Authorization Key
2020-11-12 13:09:26 -05:00
in your external service.
1. _(Optional)_ To generate a test alert to test the new integration, enter a
sample payload, then click **Save and test alert payload** .Valid JSON is required.
1. Click **Save Integration** .
The new HTTP Endpoint displays in the [integrations list ](#integrations-list ).
You can edit the integration by selecting the ** {pencil}** pencil icon on the right
side of the integrations list.
2020-10-05 20:09:01 -04:00
### External Prometheus integration
2020-11-12 13:09:26 -05:00
For GitLab versions 13.1 and greater, please read
[External Prometheus Instances ](../metrics/alerts.md#external-prometheus-instances )
to configure alerts for this integration.
2020-10-05 20:09:01 -04:00
2020-11-12 13:09:26 -05:00
## Customize the alert payload outside of GitLab
2020-10-01 14:10:20 -04:00
2020-11-12 13:09:26 -05:00
For all integration types, you can customize the payload by sending the following
parameters. All fields other than `title` are optional:
2020-10-01 14:10:20 -04:00
| Property | Type | Description |
| ------------------------- | --------------- | ----------- |
| `title` | String | The title of the incident. Required. |
| `description` | String | A high-level summary of the problem. |
2020-11-12 13:09:26 -05:00
| `start_time` | DateTime | The time of the incident. If none is provided, a timestamp of the issue is used. |
2020-10-01 14:10:20 -04:00
| `end_time` | DateTime | For existing alerts only. When provided, the alert is resolved and the associated incident is closed. |
| `service` | String | The affected service. |
| `monitoring_tool` | String | The name of the associated monitoring tool. |
| `hosts` | String or Array | One or more hosts, as to where this incident occurred. |
| `severity` | String | The severity of the alert. Must be one of `critical` , `high` , `medium` , `low` , `info` , `unknown` . Default is `critical` . |
| `fingerprint` | String or Array | The unique identifier of the alert. This can be used to group occurrences of the same alert. |
| `gitlab_environment_name` | String | The name of the associated GitLab [environment ](../../ci/environments/index.md ). This can be used to associate your alert to your environment. |
You can also add custom fields to the alert's payload. The values of extra
parameters aren't limited to primitive types (such as strings or numbers), but
can be a nested JSON object. For example:
```json
{ "foo": { "bar": { "baz": 42 } } }
```
2020-11-12 13:09:26 -05:00
TIP: **Tip:**
Ensure your requests are smaller than the
[payload application limits ](../../administration/instance_limits.md#generic-alert-json-payloads ).
2020-10-01 14:10:20 -04:00
Example request:
```shell
curl --request POST \
--data '{"title": "Incident title"}' \
--header "Authorization: Bearer < authorization_key > " \
--header "Content-Type: application/json" \
< url >
```
2020-10-05 20:09:01 -04:00
The `<authorization_key>` and `<url>` values can be found when configuring an alert integration.
2020-10-01 14:10:20 -04:00
Example payload:
```json
{
"title": "Incident title",
"description": "Short description of the incident",
"start_time": "2019-09-12T06:00:55Z",
"service": "service affected",
"monitoring_tool": "value",
"hosts": "value",
"severity": "high",
"fingerprint": "d19381d4e8ebca87b55cda6e8eee7385",
"foo": {
"bar": {
"baz": 42
}
}
}
```
## Triggering test alerts
> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/3066) in GitLab Core in 13.2.
2020-10-05 20:09:01 -04:00
After a [project maintainer or owner ](../../user/permissions.md )
configures an integration, you can trigger a test
2020-10-01 14:10:20 -04:00
alert to confirm your integration works properly.
1. Sign in as a user with Developer or greater [permissions ](../../user/permissions.md ).
1. Navigate to **Settings > Operations** in your project.
1. Click **Alerts endpoint** to expand the section.
1. Enter a sample payload in **Alert test payload** (valid JSON is required).
1. Click **Test alert payload** .
GitLab displays an error or success message, depending on the outcome of your test.
## Automatic grouping of identical alerts **(PREMIUM)**
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/214557) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.2.
In GitLab versions 13.2 and greater, GitLab groups alerts based on their
payload. When an incoming alert contains the same payload as another alert
(excluding the `start_time` and `hosts` attributes), GitLab groups these alerts
2020-11-08 22:09:03 -05:00
together and displays a counter on the [Alert Management List ](incidents.md )
2020-10-01 14:10:20 -04:00
and details pages.
If the existing alert is already `resolved` , GitLab creates a new alert instead.
2020-11-08 22:09:03 -05:00
![Alert Management List ](img/alert_list_v13_1.png )
2020-10-13 20:08:48 -04:00
2020-10-15 20:08:56 -04:00
## Link to your Opsgenie Alerts
2020-10-13 20:08:48 -04:00
2020-11-03 19:09:12 -05:00
DANGER: **Deprecated:**
We are building deeper integration with Opsgenie and other alerting tools through
[HTTP endpoint integrations ](#generic-http-endpoint ) so you can see alerts within
the GitLab interface. As a result, the previous direct link to Opsgenie Alerts from
2020-11-18 19:09:41 -05:00
the GitLab alerts list is scheduled for deprecation following the 13.7 release on December 22, 2020.
2020-11-03 19:09:12 -05:00
2020-10-13 20:08:48 -04:00
> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/3066) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.2.
You can monitor alerts using a GitLab integration with [Opsgenie ](https://www.atlassian.com/software/opsgenie ).
If you enable the Opsgenie integration, you can't have other GitLab alert
services, such as [Generic Alerts ](generic_alerts.md ) or Prometheus alerts,
active at the same time.
To enable Opsgenie integration:
1. Sign in as a user with Maintainer or Owner [permissions ](../../user/permissions.md ).
1. Navigate to **Operations > Alerts** .
1. In the **Integrations** select box, select **Opsgenie** .
1. Select the **Active** toggle.
1. In the **API URL** field, enter the base URL for your Opsgenie integration,
such as `https://app.opsgenie.com/alert/list` .
1. Select **Save changes** .
After you enable the integration, navigate to the Alerts list page at
**Operations > Alerts**, and then select **View alerts in Opsgenie** .