Opsgenie: an alert per synthetic-monitor alert, through the Alert API
An Opsgenie alert sink posts to the Alert API URL you paste, authenticated with an Authorization: GenieKey header carrying your integration key, whenever a synthetic monitor raises an alert at or above your minimum severity.
Which way the data flows
Dokimore to Opsgenie only; alerts are created, never read or closed.
Set it up
- In Opsgenie, add an API integration to the team and copy its key and the Alert API URL for your region.
- In Developer Experience, open Monitoring, then Alert Sinks, and add an Opsgenie sink with the URL, the key and a minimum severity.
- Let a synthetic monitor raise an alert, and confirm that it reaches the right team.
Where it stops
Stated plainly
- Alerts are created, not closed; close them in Opsgenie or with its own rules.
- The key is stored encrypted in the alert sink record and sent only in the Authorization header.
Questions buyers ask
Do failed test runs create Opsgenie alerts?
No. Only synthetic-monitor alerts reach a sink today, and bot alerting does not send to Opsgenie.
Which region URL do I paste?
The Alert API URL for the Opsgenie region your account lives in; the sink posts to exactly the URL you give.
Where it is implemented
The files in our code that carry this integration. A catalogue test checks that each still exists, so this page cannot outlive the feature.
backend/src/modules/developer-experience/services/alert-sink-dispatcher.tsbackend/src/modules/developer-experience/routes/alert-sinks.tsbackend/src/modules/developer-experience/services/synthetic-monitoring.ts
Related pages
- CI/CD integration guide
- Visual and web intelligence
- Every integration, by job
- Opsgenie: Opsgenie Alert API (the vendor’s documentation, read 2026-11-10)
Also under Alerting and chat: Slack · Microsoft Teams · PagerDuty · Webhooks
Try it against your own pipeline
Free plan, no card; the integrations on this page are on every plan.