Skip to content
downpipes docs

Send downpipes alerts to Opsgenie

Opsgenie receives downpipes alerts through its Alert API. The engine posts each event to your Opsgenie alerts endpoint, authenticated with an API integration key. A failing or stale downpipe opens an alert, and when the downpipe recovers, downpipes closes that same alert by its alias, so an operator sees it close rather than linger.

If you are setting this up new, consider Jira Service Management instead: Atlassian plans to retire Opsgenie around 5 April 2027 in favour of it. The downpipes channel is the same for both, so the Jira Service Management guide is the same steps pointed at the JSM endpoint.

What you need

  • An Opsgenie account where you can add an API integration and read its API key.
  • Access to the downpipes console with the notify-config capability (Operator, Approver or Owner), and your Opsgenie region to hand (the endpoint differs for a US-hosted versus an EU-hosted tenant).

Set it up

  1. In Opsgenie, add an API integration (Settings, Integrations, then add an API integration) and turn it on.
  2. Copy the integration’s API key.
  3. Note your alerts endpoint. It is https://api.opsgenie.com/v2/alerts for a US-hosted tenant, or https://api.eu.opsgenie.com/v2/alerts for an EU-hosted one. If you are unsure which region your account is on, check it in the Opsgenie console.
  4. In the downpipes console, open Notifications, choose Add a channel and pick Jira Service Management / Opsgenie (Alert API). Adding a channel needs the notify-config capability, so an Operator, Approver or Owner can add one.
  5. Paste your alerts endpoint into the URL field and the API key into the GenieKey API token field. downpipes sends the token to Opsgenie in the request’s Authorization header as GenieKey <token> and seals it at rest, so it is never shown again. Name the channel and save it, then a rule routes events to it.
  6. Choose Test on the channel row to confirm delivery without sending real alert content, then check the alert reached Opsgenie.

Good to know

  • Dedup and close run on the alias. downpipes sends a stable alias built from the downpipe and the event, so a repeated condition de-duplicates onto the open alert and a recovery closes that same alert by its alias. The body carries a short message, a mapped priority and a source label, never backup contents or a secret.
  • Opsgenie is on a retirement path. Atlassian plans to retire Opsgenie around 5 April 2027 in favour of Jira Service Management. A new setup can point the same channel at the JSM endpoint instead; see the Jira Service Management guide.

Last updated .