Set up Opsgenie alerts
Opsgenie integration works like PagerDuty: a Down alert creates an Opsgenie alert, and the matching Up alert
closes it. Under the hood an Opsgenie contact would be an http contact with its gateway set to Opsgenie
and its address holding an API key (a key, not a URL).
Settings reference
Section titled “Settings reference”| Setting (UI label) | API field (v2) | Type / allowed values | Default | Plan limits | What it does for you |
|---|---|---|---|---|---|
| Contact Type | type |
"http" |
- | - | Opsgenie is stored as a plain http contact |
| Gateway | gateway |
"Opsgenie" |
- | - | Routes through the Opsgenie Alerts API create/close flow |
| API key | address |
The Opsgenie API integration key (not a URL) | - | - | Identifies the Opsgenie team the alert pages |
groupedAlerts will have no effect on this channel once it ships - see below.
Add an Opsgenie contact (once available)
Section titled “Add an Opsgenie contact (once available)”- In Opsgenie, create an API integration for the team that should receive HostTracker alerts, and copy its API key.
- In HostTracker, open Contacts and click Add contact.
- Choose Opsgenie.
- Paste the API key and give the contact a name.
- Save.
How it behaves
Section titled “How it behaves”- A Down alert creates a new Opsgenie alert; the matching Up alert closes it automatically.
- On-call channels are never grouped - every Down and Up is sent as its own event so nothing gets folded
into a summary message, regardless of the contact’s
groupedAlertssetting. See grouped alerts.
Do it with the API or MCP
Section titled “Do it with the API or MCP”The type is registered (GET /contact/type lists it, creatable: false), but creating one is refused today
with 422 contact_type_not_creatable. There’s no API or MCP workaround while the channel is parked.
Limits and gotchas
Section titled “Limits and gotchas”- Not creatable today - see the caution above.
- Once available: paste the API key exactly as Opsgenie gives it, with no extra scheme or whitespace, and test the contact after setup to confirm a real alert appears in Opsgenie.
- As a recognized gateway, Opsgenie is already wired to receive certificate-expiry, domain-expiry, DNSBL blacklist and Web Risk notices once creation ships - the delivery logic doesn’t wait on that fix, only contact creation does.