Page Comparison

...

Overview

What does the integration offer?

Use the Azure Resource Health Integration to forward Azure Resource Health alerts to Jira Service Management. Jira Service Management determines the right people to notify based on on-call schedules- using email, text messages (SMS), phone calls, iOS & Android push notifications, and escalates alerts until the alert is acknowledged or closed.

How does the integration work?

When a Resource Health alert is created in Azure, an alert is automatically created in Jira Service Management. The alert is closed in Jira Service Management if the Resource Health alert is closed in Azure.

Set up the integration

Azure Resource Health is an API-based integration. Setting it up involves the following steps:

• Add an Azure Resource Health integration in Jira Service Management

• Configure the integration in Azure Resource Health

Add Azure Resource Health integration

To add an Azure Resource Health integration in Jira Service Management:

1. Go to your team’s operations page.

2. On the left navigation panel, select Integrations and then Add integration.

3. Run a search and select “Azure Resource Health”.

4. On the next screen, enter aname for the integration.

5. Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.

6. Select Continue.
   The integration is saved at this point.

7. Expand the Steps to configure the integration section and copy the URL generated for your account.
   You will use this URL while configuring the integration in Azure later.

8. Select Turn on integration.
   The rules you create for the integration will work only if you turn on the integration.

Configure the integration in Azure Resource Health

1. In the Azure Portal, select Browse.

2. Select Service Health.

3. In the Resource Health section, select Resource Health.

4. Open Add resource health alert.

5. Add conditions for filtering alerts.

6. Go to the Actions tab.

7. Select Create Action Group.
   While adding actions, select Webhook for the action type.

8. Paste the URL you copied while adding the integration in Jira Service Management into URI.

9. Enable the common alert schema if required.

10. Save the changes for the new action group.

11. Save the changes for the alert.

Sample payload

{
  "schemaId": "Microsoft.Insights/activityLogs",
  "data": {
    "status": "Activated",
    "context": {
      "activityLog": {
        "channels": "Admin, Operation",
        "correlationId": "a1be61fd-37ur-ba05-b827-cb874708babf",
        "eventSource": "ResourceHealth",
        "eventTimestamp": "2018-09-04T23:09:03.343+00:00",
        "eventDataId": "2b37e2d0-7bda-4de7-ur8c6-1447d02265b2",
        "level": "Informational",
        "operationName": "Microsoft.Resourcehealth/healthevent/Activated/action",
        "operationId": "2b37e2d0-7bda-489f-81c6-1447d02265b2",
        "properties": {
          "title": "Virtual Machine health status changed to unavailable",
          "details": "Virtual machine has experienced an unexpected event",
          "currentHealthStatus": "Unavailable",
          "previousHealthStatus": "Available",
          "type": "Downtime",
          "cause": "PlatformInitiated"
        },
        "resourceId": "/subscriptions/<subscription Id>/resourceGroups/<resource group>/providers/Microsoft.Compute/virtualMachines/<resource name>",
        "resourceGroupName": "<resource group>",
        "resourceProviderName": "Microsoft.Resourcehealth/healthevent/action",
        "status": "Active",
        "subscriptionId": "<subscription Id>",
        "submissionTimestamp": "2018-09-04T23:11:06.1607287+00:00",
        "resourceType": "Microsoft.Compute/virtualMachines"
      }
    }
  }
}

...

See also

Explore integration types

Explore integration actions

Add integration rules