Skip to content
downpipes docs

Send downpipes alerts to Jira Service Management

Jira Service Management receives downpipes alerts through its Operations Alert API, the same Alert API Opsgenie exposes (JSM Operations absorbed Opsgenie’s alerting). The engine posts each event to the JSM Operations integration endpoint, authenticated with a GenieKey-style integration key. A failing or stale downpipe opens an alert, and a recovery closes that same alert by its alias.

Because the engine makes the outbound call, a Cloudflare Access perimeter on your console never blocks delivery. If Jira Service Management is not your alerting stack, the full integration catalogue on the website lists every notification channel downpipes supports.

What you need

  • A Jira Service Management site with Operations, where you can add an API integration and read its key.
  • Access to the downpipes console with the notify-config capability (Operator, Approver or Owner) to add and test the channel.

Set it up

  1. In JSM, open Operations, add an API integration, and turn it on.
  2. Copy the integration key it issues.
  3. Note the Operations alerts endpoint, https://api.atlassian.com/jsm/ops/integration/v2/alerts. Confirm the exact host in your JSM console if your site shows a different one.
  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 the endpoint into the URL field and the integration key into the GenieKey API token field. downpipes sends it in the request’s Authorization header as GenieKey <token> and seals it at rest, never showing it 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 appeared in JSM Operations.

Good to know

  • Same mechanism as Opsgenie. The alias-based dedup and close-by-alias are the same as the Opsgenie channel, because JSM Operations and Opsgenie share the Alert API. If you already run the Opsgenie channel, this is the same channel kind pointed at the JSM endpoint.
  • A create is accepted asynchronously. JSM answers an alert create with an accepted-for-processing response rather than an immediate confirmation, so downpipes checks the request status once to confirm the alert really landed, and records the delivery as unconfirmed rather than claiming success if it cannot.

Last updated .