• Products
  • Get started
  • Documentation
  • Resources

Integrate with Compose

If you’re a customer who shifted your operations from Opsgenie to Jira Service Management, adding new instances of this integration isn’t possible in Jira Service Management. You can only edit the integrations that originally shifted from Opsgenie.

Compose logo

What does Jira Service Management offer Compose users?

Compose sends alerts via email and using webhook. Either method is used to forward Compose alerts to Jira Service Management. How to create alerts via email in Jira Service Management is described in the email integration document. This document describes how to integrate Compose and Jira Service Management using the Compose integration.

Jira Service Management provides a specific API for Compose Integration to create alerts directly in Jira Service Management data centers.

Functionality of the integration

  • When Compose triggers an alert, an alert is created in Jira Service Management automatically through the integration.

Edit Compose integration in Jira Service Management

To edit a Compose integration in Jira Service Management, complete the following steps:

  1. Go to your team’s operations page.

  2. On the left navigation panel, select Integrations.

  3. Search for your Compose integration.

  4. Edit the integration settings and rules as necessary.

Configure the integration in Compose

Use the instructions in this section if applicable.

  1. From the Compose control panel, open Account->Notifications page.

  2. From this page, select Webhook as the type of the notification.

  3. Under Webhook Alerts, populate Webhook Url field with the integration URL copied when saving the integration.

  4. Click Save alert settings.

Screenshot_Compose alert settings

5. Alert properties are configured from Compose Integration / Advanced Settings page.
​6. Now manage your Compose database alerts at Jira Service Management and leverage its full alerting functionality.

Sample payload sent from Jira Service Management


1 2 3 4 5 6 7 8 9 10 11 12 { "alert_type_causes": "Some common causes are: * Network connectivity interuption * Server Failure * High load on primary", "alert_type_description": "A stepdown alert is raised when the primary member in a replica set is unavailable and a secondary is promoted to primary.", "alert_type_resolution": "There is generally nothing to do to resolve this type of alert. This is the expected behavior, but you should make sure that your app is configured to handle this type of failure by using a replica set in your connection info and using safe writes. Most drivers will recover automatically from this. If not an app restart might be required.", "databases[]": "db1,db2", "message": "There was a stepdown c235.candidate.17.mongolayer.com:10235 -> c235.candidate.16.mongolayer.com:10235", "severity": "1", "source": "candidate.16.mongolayer.com:10235", "title": "stepdown alert on candidate.16.mongolayer.com:10235", "trigger_value": "The value that was triggered causing the alert. This only applies to alerts with limits.", "type": "stepdown" }


Additional Help