Connect Opsgenie
Firefight has a dedicated alert source for Opsgenie. Each Opsgenie alert becomes a Firefight alert that resolves when it is closed in Opsgenie, and the same source tells Firefight when someone acknowledges a page or adds a note to it.
Set up the Firefight side
Section titled “Set up the Firefight side”Go to Settings → Alert Sources, click Add source, give it a name like “Opsgenie”, and pick the Opsgenie provider. When you create it, Firefight opens the source’s setup. It shows the ingest URL and a Copy token button for the source’s secret token, and the same steps as this page.
Set up the Opsgenie side
Section titled “Set up the Opsgenie side”- In Opsgenie, add a Webhook integration with the ingest URL, and send the alert description with it.
- Post to the URL when an alert is created, acknowledged or closed, and when a note is added to it.
- Add a custom header named
X-Firefight-Tokenholding the token.
Requests that fail the check are rejected with 401, and the source’s row in Settings → Alert Sources shows the rejection. Firefight accepts and ignores every other action, such as a new tag.
What Firefight reads
Section titled “What Firefight reads”Each alert gets these fields, which you can match in your routing rules.
| Field | Value |
|---|---|
title | The alert’s message |
description | The alert’s description |
service | The alert’s entity |
severity_raw | The alert’s priority, such as P1 |
Opsgenie sends no address for an alert’s page, so these alerts have no link back to Opsgenie. Map Opsgenie’s priorities to your severities in the source’s Severity map.
Firing and resolving
Section titled “Firing and resolving”A created alert fires and a closed one resolves. Every action on the same Opsgenie alert lands on the same Firefight alert.
Pages kept in step
Section titled “Pages kept in step”When an Opsgenie alert joins a Firefight incident, or when Firefight raised the page itself, the page and the incident stay in step. An acknowledgement or a note in Opsgenie shows on the incident’s timeline, named for the member who did it when their Opsgenie user is their Firefight email. A page Firefight raised comes back through this source as an alert and joins the incident it was raised for, so it never opens a second one.
Changes in the other direction, such as resolving the incident in Firefight closing the alert in Opsgenie, go through an Opsgenie connection under Integrations. See Halon on call for raising pages and everything that stays in step.
See Grouping & deduplication for how repeat firings collapse into one alert.