Create Opsgenie Alerts from Incidents

Create an API integration

1. In Opsgenie, open Settings → Integrations (or a team's Integrations tab) and add an API integration.
2. Give it a name such as "SutramX", assign it to the right team, and save.
3. Copy the API key of the integration.

Pick the right region

When you connect, choose US or EU to match your Opsgenie account. If you sign in at app.eu.opsgenie.com, choose EU. Otherwise choose US.

How incidents flow

• Monitor goes down: an Opsgenie alert is created.
• Incident acknowledged in SutramX: the alert is acknowledged, with the note "Acknowledged in SutramX by <name>".
• Monitor recovers: the alert is closed automatically, with the note "Monitor recovered".
• An escalation step that targets Opsgenie creates the alert again under the same alias, so it lands on the existing alert.

Each SutramX incident maps to exactly one Opsgenie alert, using the alias sutramx-<incident id>. The sync is one-way: acknowledging or closing the alert in Opsgenie does not change the incident in SutramX.

What Opsgenie receives

Every alert is created with priority P1 and source SutramX. The message is the monitor name with "is DOWN", cut to Opsgenie's 130-character limit; the full text, with URL, region, failure detail and a link to the incident, is in the description.

{
  "message": "Checkout API is DOWN",
  "alias": "sutramx-<incident id>",
  "description": "[DOWN] Checkout API is DOWN\nURL: https://api.example.com/health\nRegion: FRA1 (Frankfurt, Germany)\nDetail: <failure reason>\nDetails: <link to the incident>",
  "source": "SutramX",
  "priority": "P1",
  "details": {
    "monitor_name": "Checkout API",
    "monitor_url": "https://api.example.com/health",
    "region": "FRA1 (Frankfurt, Germany)",
    "incident_id": "<incident id>"
  }
}

Opsgenie only receives real incidents. SSL and domain reminders, maintenance and other notices never create an alert.

Test the connection

Tests never run automatically, because they create a real alert. Open the connection's menu, choose Send test and confirm. SutramX creates a test alert, which may notify whoever is on call, and closes it a few seconds later. If the close step fails, the result says so; close the test alert yourself in Opsgenie.

Routing and escalation

You can connect up to 10 Opsgenie integrations, for example one per team, and give each its own routing (all monitors, selected groups or selected monitors). Recoveries ignore routing, so an alert that was opened is always closed. Opsgenie can also be a step in a SutramX escalation policy (on Growth and Pro); such a step goes to every Opsgenie connection, regardless of routing.

Troubleshooting

• "OpsGenie responded 401" or "403": the API key is wrong, was deleted, or lacks create and update access. Also check that the region matches your account.
• Alerts open but never close: check the incident's Notifications list in SutramX for the recovery delivery and its error.
• No acknowledgement in Opsgenie: it is only sent when the down alert reached Opsgenie, and only for the first acknowledgement of an incident.
• The connection shows Failing: the last 3 deliveries failed. Replace the key with Edit, then send a test.

Moving off Opsgenie? The import wizard in the dashboard (Import from another tool) connects with an Opsgenie API key and imports your schedules, escalation policies and heartbeats after a preview. Heartbeats become heartbeat monitors with new ping URLs to swap into your jobs.

Common questions

Which access does the API key need?

Create and Update Access. Read access is not needed.

Can I change the alert priority?

Every alert is created as P1. Use routing so only the monitors that should page are sent to Opsgenie, and Opsgenie's own rules if you need to change priority there.

Connect it in SutramX

1. Sign in to the SutramX dashboard and open Integrations & API in the sidebar, then the Integrations tab.
2. On the Opsgenie card, click Connect. Where you see "Connect with …", you just sign in and approve. Otherwise the card shows two or three short steps and one box to paste into.
3. Already have a webhook link? Paste it into the box at the top of the page and SutramX works out which service it belongs to.
4. SutramX sends a test straight away so you can confirm delivery before any real incident.
5. Optional: use Routing to send only some monitors or groups to this channel.

You can connect more than one Opsgenie destination. Each connection has its own routing, so different channels can receive different monitors.

Other incident and developer integrations

• GitHub issues alerts setup: Open an issue on downtime, close it on recovery.