Opsgenie integration¶
Connecting Opsgenie gives DXDT on-call and alerting visibility — open alerts, on-call schedules, who is currently on call, and teams — to complement PagerDuty for incident response. The integration is strictly read-only.
| Setup time | ~5 minutes |
| Difficulty | Easy |
Access required: Admin or an integration owner, to create a read-only API key
Prerequisites¶
- An Opsgenie account with permission to create API integrations
- Knowing whether your account is on the US or EU instance
Setup¶
1. Open the API integration settings¶
In Opsgenie, go to Settings > Integrations (or Teams > [your team] > Integrations) and add an API integration, or open an existing one to reuse its key.
Note
Use a dedicated API integration for DXDT so you can revoke it independently.
2. Restrict the key to read access¶
In the API integration's configuration, enable only the Read access right and leave create/update/delete/execute actions unchecked. Save the integration.
Note
Grant Read only — DXDT never creates, acknowledges, closes or modifies alerts.
3. Copy the API key and note your region¶
Copy the generated API Key from the integration. Determine your region: the default us uses api.opsgenie.com, while eu uses api.eu.opsgenie.com. If your Opsgenie login URL is on .eu, set the region to eu.
- The key is sent as
Authorization: GenieKey <api_key>. - Region is optional and defaults to
usif left blank.
Configuration fields¶
| Field | Where to find it |
|---|---|
API Key (api_key) |
The API key from your Opsgenie API integration (Settings > Integrations). Required. |
Region (region) |
us (default, api.opsgenie.com) or eu (api.eu.opsgenie.com). Optional; defaults to us if left blank. |
Verify the connection¶
Enter the API key (and region if EU) in the Opsgenie plugin's Configuration tab and click Install & Configure; the Live Status panel should show a healthy connection and your Opsgenie account name.
Security
Your Opsgenie API key is stored encrypted per-tenant and is used only for read-only Opsgenie API operations.
Troubleshooting¶
401 / Unauthorized
The API key is wrong, disabled, or belongs to a different Opsgenie region. Re-copy the key from the API integration and confirm the region matches your instance (eu vs us).
Empty results but healthy status
The integration's read access is scoped to a single team with no matching alerts/schedules. Use an account-level API integration with Read access, or point it at a team that has alerts and schedules.
Requests time out or return the wrong data
Region mismatch — an EU account queried against the US endpoint. Set the Region field to eu.
Vendor documentation: https://support.atlassian.com/opsgenie/docs/api-key-management/