Deployment integrations

Deployment pipelines receive events from your CI/CD tooling so ilert can show the reader what changed shortly before an alert fired.

A deployment pipeline is to deployment events what an alert source is to alerts: the object that receives them, holds the integration key they are routed by, and decides which of them are worth recording.

Its purpose is correlation. When an alert fires, ilert looks for deployments that landed shortly before it and attaches the closest ones to the alert, so the responder opens a page that already answers what changed just now — usually the first question anyone asks. See Deployment events for how that matching works and how teams narrow it.

Every plan includes deployment events.

Create a deployment pipeline

Every integration on this page starts here; only the vendor-side setup differs.

1

Open the pipeline list

In the sidebar, go to Alerting → Deployment events, then select the Deployment pipelines tab. Click Create new pipeline.

2

Name it and choose a type

Type decides the rest of the form. With GitHub chosen it grows branch and event filters — and the branch filter arrives already populated.

Field	What it does
Teams	Which teams own the pipeline. This is also what lets a team claim its own deployments for correlation
Name	How the pipeline appears in the list and on correlated alerts
Type	The tool sending the events. It cannot be changed after creation, and it governs which filters the form offers

Branch filters start filled in. A new GitHub, GitLab, or Azure DevOps pipeline arrives with main and master already in Branch filters, so events from every other branch are dropped without a trace. That is usually what you want. If it is not — you deploy from release branches, or want everything — clear the field: empty means all branches, not none.

3

Create it and copy the URL

Click Create. The pipeline's detail view shows its Integration key and the webhook URL built from it. That URL is what you paste into the vendor.

4

Send a deployment and confirm it arrived

Trigger whatever you configured — push a commit, publish a release — and check that a row appears under Alerting → Deployment events.

This step is not optional. The events API answers 202 Accepted to any request, including one carrying an invalid integration key, so nothing on the sending side will tell you the pipeline never received it.

What each type supports

The Type you pick decides which filters exist, because a filter can only be built from what the vendor's payload actually carries.

Type	Branch filters	Event filters	Setup
GitHub	Yes	Pull request (merged), Commit (push), Release (published)	GitHub deployment pipeline
GitLab	Yes	Push hook, Merge request hook, Release hook	GitLab deployment pipeline
Azure DevOps	Yes	—	Azure DevOps deployment pipeline
Argo CD	—	—	Argo CD deployment pipeline
API	—	—	API deployment pipeline

Both filters are subtractive, and an empty filter means keep everything rather than keep nothing:

• Branch filters — a chip list of branch names. Prefilled with main and master.
• Event filters — a checkbox list of the vendor's event types. Empty by default, so everything the webhook sends is recorded.

Filtering in ilert rather than at the vendor is what makes one account-wide webhook workable: point every repository at one URL, then let each pipeline keep only what concerns it.

Prefer release events where the tool offers them. They map one-to-one onto things you actually shipped, which is what makes a correlation meaningful. Push events from an account-wide webhook can arrive hundreds a day and correlate with everything and nothing.

Manage a pipeline

The detail view carries three things worth knowing about:

• Rotate key issues a new integration key. The old one stops working immediately, so update the vendor's webhook in the same sitting.
• Export to Terraform emits the pipeline as a resource block, for accounts managed as code.
• Integration guide links back to the setup page for that type.

In this section

API deployment pipeline

Post deployment events from anything that can make an HTTP request.

GitHub deployment pipeline

A webhook or the ilert GitHub Action.

GitLab deployment pipeline

A group or project webhook.

Azure DevOps deployment pipeline

A project service hook.

Argo CD deployment pipeline

The notifications controller, for GitOps rollouts.