Skip to main content
The Opsgenie integration opens an Opsgenie alert for each selected issue and keeps it in sync:
  • Setting a status on the issue (for example Investigating) acknowledges the Opsgenie alert.
  • Reset on the issue unacknowledges it.
  • When the issue closes, the Opsgenie alert is closed.

​
Setting Up in Opsgenie

  1. Go to the Teams section and select the team you want to integrate with Opsgenie.
  2. Click on the Integrations tab.
  3. Click on the Add Integration button.
  4. From the list of products, select API.
  5. Enter the integration name (e.g., Coalesce Quality) and select the assignee team.
  6. Click the Continue button.
  7. Copy the API Key and save it for later use.
  8. Click the Turn on Integration button and ensure the integration status is set to ON.

​
Setting up in Coalesce Quality

  1. Go to the page.
  2. Click on the Add Integration button.
  3. Select Opsgenie from the list of platforms.
  4. Enter the API Key obtained from the Opsgenie setup and select the appropriate region (EU or US).
  5. Choose the severity of issues and the assets for which alerts should be sent to Opsgenie.
  6. Click the Create button to complete the integration setup.

​
Checking that alerts arrive

Every alert Coalesce Quality sends to Opsgenie is recorded under Settings > Integrations > your Opsgenie integration > Deliveries: the request made to the Opsgenie API, the response it returned, and the reason when nothing was sent. Use Send test event to open a real test alert and see the outcome, and Redeliver to send an earlier event again once you have changed something. An invalid or revoked API Key shows up there as a rejected request rather than as silence, which is the usual reason alerts stop arriving. See Debugging Deliveries. Opsgenie receives issue and incident lifecycle events. A delivery skipped as Event type unsupported by integration or No action for lifecycle state is an event that has no Opsgenie equivalent. It is not an error.