GitLab

Connect DevHelm to GitLab’s built-in Alert Management through an HTTP endpoint integration. DevHelm POSTs each incident to the endpoint GitLab generates; alerts appear under Operations → Alerts and can automatically open GitLab incidents if your project is configured to do so. Works with GitLab.com and self-hosted GitLab (13.1+). The endpoint URL must use HTTPS.

Setup

Create an HTTP endpoint integration in GitLab

You need at least the Maintainer role on the project.

In your GitLab project, go to Settings → Monitor and expand the Alerts section
Click Add new integration and select HTTP Endpoint as the integration type
Name the integration and toggle Active on, then Save integration
Open the View credentials tab and copy the URL and the Authorization Key

The URL looks like https://gitlab.com/{namespace}/{project}/prometheus/alerts/notify.json (or the equivalent path on a self-hosted instance).

Create the alert channel in DevHelm

devhelm alert-channels create \
  --name "GitLab Alerts" \
  --type gitlab \
  --config '{"channelType":"gitlab","endpointUrl":"https://gitlab.com/your-group/your-project/prometheus/alerts/notify.json","authorizationKey":"your-gitlab-authorization-key"}'

alertChannels:
  - name: GitLab Alerts
    config:
      channelType: gitlab
      endpointUrl: ${GITLAB_ALERT_ENDPOINT_URL}
      authorizationKey: ${GITLAB_ALERT_AUTH_KEY}

Test the channel

devhelm alert-channels test <channel-id>

Configuration

Field	Description	Required
`endpointUrl`	HTTP endpoint URL from the GitLab alert integration’s View credentials tab	Yes
`authorizationKey`	Authorization key from the same integration	Yes

Lifecycle behavior

GitLab uses a trigger-resolve lifecycle, keyed on a per-incident fingerprint (devhelm-<incident id>) so repeated events about the same incident map to the same GitLab alert:

DevHelm event	GitLab action
Incident created	Fires a new alert (`monitoring_tool: DevHelm`)
Incident resolved	Sends `end_time`, so GitLab auto-resolves the matching alert
Incident reopened	Fires the alert again under the same fingerprint

If your project links the integration to incident creation, GitLab opens (and can auto-close) an incident alongside the alert.

Troubleshooting

Channel creation fails with an HTTPS error

The endpoint URL must start with https://. Copy it exactly as shown in GitLab’s View credentials tab.

GitLab returns 401 or 403

The authorization key doesn’t match the integration. Re-copy it from Settings → Monitor → Alerts → (your integration) → View credentials, and make sure you paired it with the URL from the same integration.

Alerts aren't appearing in GitLab

Confirm the integration’s Active toggle is on — a disabled integration rejects deliveries
Use the integration’s Send test alert tab in GitLab to confirm the endpoint itself works, then run devhelm alert-channels test <id>
On self-hosted GitLab, ensure the instance presents a valid SSL certificate, since DevHelm only posts over HTTPS

Overview

Alert Channels

CI/CD

Setup

Configuration

Lifecycle behavior

Troubleshooting

​Setup

​Configuration

​Lifecycle behavior

​Troubleshooting

Setup

Configuration

Lifecycle behavior

Troubleshooting