Jira Service Management Integration

Jira Service Management (JSM) Operations routes alerts to on-call teams with schedules and escalation policies. Cronitor creates a JSM alert when a monitor fails and closes it when the monitor recovers.

From Jira Service Management:

  1. Open your service project and go to Operations, then the team you want to receive Cronitor alerts.
  2. Open the team's Integrations page and click Add integration.
  3. Select the API integration, give it a name such as "Cronitor", and save it.
  4. Make sure the integration is turned on, then copy its API key. You'll need it in Cronitor.

From Cronitor:

  1. From the Settings > Integrations page, click the Create Integration button and select Jira Service Management.
  2. Give this integration a name. This will be used in the Cronitor UI.
  3. Give this integration a unique identifier. This can be used in the Cronitor API.
  4. Paste the JSM API key into the API Key field and complete the integration.
  5. Select this integration from the Jira Service Management dropdown under the "integrations" tab when creating or editing a monitor or notification list.

What Cronitor sends

Cronitor calls the JSM Operations alert API at https://api.atlassian.com/jsm/ops/integration/v2/alerts with the header Authorization: GenieKey <API key>.

  • A failure opens an alert on the alias <monitor code>-<environment key>. The alert message is the monitor name and what happened, up to 130 characters. The description has the details, and details.link opens the monitor or issue in Cronitor.
  • A recovery closes the alert on that same alias. The close note is the recovery message. The monitor's note is sent with the failure alert, not with the close.
  • A run, a complete, and a tick are priority P5 (informational) on the alias <code>-<environment key>:notice. JSM deduplicates open alerts by alias, so a notice never counts against, closes, or acknowledges the paging alert. Cronitor never closes the notice alert; later notices are deduplicated into it until it is closed in JSM.

The kind of issue, e.g. Failed Execution, Missed Execution or SSL Expiring, is in details.issue_type. Alert policies and routing rules can match on it.

From the API

Create this destination with the Integrations API using the service key jira and the field key. Add it to a notification list under the key jira.