Integrate Opsgenie with Microsoft Azure
Overview
For an alert rule on a metric value, when the value of a specified metric crosses a threshold assigned, the alert rule becomes active and sends a notification. For an alert rule on events, a rule can send a notification on every event or only when a certain number of events happen.
What does the integration offer?
Azure generates alerts based on metrics and events. Opsgenie acts as a dispatcher for the alerts generated by Azure. Opsgenie determines the right people to notify based on on-call schedules and escalations and notifies via email, text messages (SMS), phone calls, and Android & iOS push notifications.
Opsgenie supports the new Azure metrics alerts as well. With the Azure new metric alerts, new fields are added to the new Azure payload. Hence, you can accordingly configure the integration to support them. Learn more about supported resources for metric alerts in Azure Monitor.
How does the integration work?
When an alert is created in Azure, an alert is automatically created in Opsgenie through the integration.
Set up the integration
Azure is an API-based integration. Setting it up involves the following steps:
Add an Azure integration in Opsgenie
Configure the integration in Azure
Add an Azure integration
If you're using Opsgenie's Free or Essentials plan or if you’re using Opsgenie with Jira Service Management's Standard plan, you can add this integration from your team dashboard only. The Integrations page under Settings is not available in your plan.
Go to Teams and select your team.
Select Integrations on the left navigation and then select Add integration.
Adding the integration from your team dashboard will make your team the owner of the integration. This means Opsgenie will assign the alerts received through this integration to your team only. Follow the rest of the steps in this section to set up the integration.
To add an Azure integration in Opsgenie:
Go to Settings > Integrations.
Select Add integration.
Run a search and select “Azure”.
On the next screen, enter a name for the integration.
Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.
Select Continue.
The integration is saved at this point.Expand the Steps to configure the integration section and copy the endpoint URL generated for your account.
You will use this URL while configuring the integration in Azure later.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
1. In the Azure Portal, select Browse.
2. Select a resource for which you want to generate alerts.
3. In the Monitor section, select Alerts.
4. Go to the Manage actions tab.
5. Select Add-action-group to create an action group.
6. While adding actions, select Webhook for the action type.
7. Paste the URL you copied while adding the integration in Opsgenie into URI.
8. Save the changes.
9. Enable the common alert schema, if required.
10. Go to Manage alert rules.
11. Create a rule or edit an existing rule.
12. Add conditions against which you want to create alerts.
13. Add the Webhook action group you created in Step 5 in the Action Group section.
14. Save the changes.
Opsgenie draggable fields providing support based on Azure schemas
Variable | AzureMonitorMetricAlert | AzureMonitorCommonAlertSchema | Azure Classic |
|---|---|---|---|
Subscription ID: {{subscription_id}} | Yes | No | Yes |
Resource group Name: {{resource_group_name}} | Yes | No | Yes |
Resource name: {{resource_name}} | Yes | No | Yes |
Status: {{status}} | Yes | Yes | Yes |
ID: {{id}} | Yes | Yes | Yes |
Name: {{name}} | Yes | No | Yes |
Condition type: {{condition_type}} | Yes | Yes | Yes |
Condition Metric Name: {{condition_metric_name}} | Yes | Yes | Yes |
Condition Metric Namespace: {{condition_metric_namespace}} | No | Yes | No |
Condition Metric Unit: {{condition_metric_unit}} | Yes | No | Yes |
Condition Metric Value: {{condition_metric_value}} | Yes | Yes | Yes |
Condition Threshold: {{condition_threshold}} | Yes | Yes | Yes |
Condition Window Size: {{condition_window_size}} | Yes | Yes | Yes |
Condition Time Aggregation: {{condition_time_aggregation}} | Yes | Yes | Yes |
Condition Operator: {{condition_operator}} | Yes | Yes | Yes |
Resource type: {{resource_type}} | Yes | No | Yes |
Resource ID: {{resource_id}} | Yes | No | Yes |
Resource region: {{resource_region}} | No | No | Yes |
Portal Link: {{portal_link}} | Yes | No | Yes |
Version: {{version}} | Yes | Yes | No |
Dimensions: {{dimensions}} | Yes | Yes | No |
SchemaId: {{schemaId}} | Yes | Yes | No |
Dimension List: {{dimensionList}} | Yes | Yes | No |
Alert Rule: {{alertRule}} | No | Yes | No |
Signal Type: {{signalType}} | No | Yes | No |
Monitor Condition: {{monitorCondition}} | No | Yes | No |
monitoring Service: {{monitoringService}} | No | Yes | No |
Alert Target IDs: {{alertTargetIDs}} | No | Yes | No |
Fired Date Time: {{firedDateTime}} | No | Yes | No |
Resolved Date Time: {{resolvedDateTime}} | No | Yes | No |
Essentials Version: {{essentialsVersion}} | No | Yes | No |
Alert Context Version: {{alertContextVersion}} | No | Yes | No |
AlertId: {{alertId}} | No | Yes | No |
Configuration Items: {{configurationItems}} | No | Yes | No |
Sample payload sent from Azure (Classic)
Create alert payload (in JSON format)
{
"status": "Activated",
"context": {
"id": "/subscriptions/1a66ce04-b633-4a0b-b2bc-a912ec8986a6/resourceGroups/montest/providers/microsoft.insights/alertrules/Alert_1_runscope12",
"name": "Alert_1_runscope12",
"description": "desc",
"conditionType": "Metric",
"condition": {
"metricName": "Memory available",
"metricUnit": "Bytes",
"metricValue": "1032190976",
"threshold": "2",
"windowSize": "5",
"timeAggregation": "Average",
"operator": "GreaterThan"
},
"subscriptionId": "1a66ce04-b633-4a0b-b2bc-a912ec8986a6",
"resourceGroupName": "montest",
"timestamp": "2015-09-18T01:02:35.8190994Z",
"resourceName": "helixtest1",
"resourceType": "microsoft.compute/virtualmachines",
"resourceId": "/subscriptions/1a66ce04-b633-4a0b-b2bc-a912ec8986a6/resourceGroups/montest/providers/Microsoft.Compute/virtualMachines/Helixtest1",
"resourceRegion": "centralus",
"portalLink": "http://portallink.com"
},
"properties": {
"hello1": "World1!",
"json_stuff": {
"type": "critical",
"color": "red"
},
"customId": "wd39ue9832ue9iuhd9iuewhd9edh",
"send_emails_to": "someone@somewhere.com"
}
}
Payload parsed by Opsgenie (in JSON format)
{
"status": "Activated",
"id": "/subscriptions/1a66ce04-b633-4a0b-b2bc-a912ec8986a6/resourceGroups/montest/providers/microsoft.insights/alertrules/Alert_1_runscope12",
"name": "Alert_1_runscope12",
"description": "desc",
"condition_type": "Metric",
"condition_metric_name": "Memory available",
"condition_metric_unit": "Bytes",
"condition_metric_value": "1032190976",
"condition_threshold": "2",
"condition_window_size": "5",
"condition_time_aggregation": "Average",
"condition_operator": "GreaterThan",
"subscription_id": "1a66ce04-b633-4a0b-b2bc-a912ec8986a6",
"resource_group_name": "montest",
"timestamp": "2015-09-18T01:02:35.8190994Z",
"resource_name": "helixtest1",
"resource_type": "microsoft.compute/virtualmachines",
"resource_id": "/subscriptions/1a66ce04-b633-4a0b-b2bc-a912ec8986a6/resourceGroups/montest/providers/Microsoft.Compute/virtualMachines/Helixtest1",
"resource_region": "centralus",
"portal_link": "http://portallink.com"
}
Sample payload sent from Azure Monitor Metric Alert Schema (New)
Create alert payload (in JSON format)
{"schemaId":"AzureMonitorMetricAlert","data":
{
"version": "2.0",
"status": "Activated",
"context": {
"timestamp": "2018-02-28T10:44:10.1714014Z",
"id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/Contoso/providers/microsoft.insights/metricAlerts/StorageCheck",
"name": "StorageCheck",
"description": "",
"conditionType": "SingleResourceMultipleMetricCriteria",
"condition": {
"windowSize": "PT5M",
"allOf": [
{
"metricName": "Transactions",
"dimensions": [
{
"name": "AccountResourceId",
"value": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/Contoso/providers/Microsoft.Storage/storageAccounts/diag500"
},
{
"name": "GeoType",
"value": "Primary"
}
],
"operator": "GreaterThan",
"threshold": "0",
"timeAggregation": "PT5M",
"metricValue": 1.0
}
]
},
"subscriptionId": "00000000-0000-0000-0000-000000000000",
"resourceGroupName": "Contoso",
"resourceName": "diag500",
"resourceType": "Microsoft.Storage/storageAccounts",
"resourceId": "/subscriptions/1e3ff1c0-771a-4119-a03b-be82a51e232d/resourceGroups/Contoso/providers/Microsoft.Storage/storageAccounts/diag500",
"portalLink": "https://portal.azure.com/#resource//subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/Contoso/providers/Microsoft.Storage/storageAccounts/diag500"
},
"properties": {
"key1": "value1",
"key2": "value2"
}
}
}
Payload parsed by Opsgenie (in JSON format)
{
"schemaId": "AzureMonitorMetricAlert",
"version": "2.0",
"status": "Activated",
"id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/Contoso/providers/microsoft.insights/metricAlerts/StorageCheck",
"name": "StorageCheck",
"description": "",
"condition_type": "SingleResourceMultipleMetricCriteria",
"condition_metric_name": "Transactions",
"condition_dimensions" : "[{name=AccountResourceId, value=/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/Contoso/providers/Microsoft.Storage/storageAccounts/diag500}, {name=GeoType, value=Primary}]",
"condition_metric_value": "1.0",
"condition_threshold": "0",
"condition_window_size": "PT5M",
"condition_time_aggregation": "PT5M",
"condition_operator": "GreaterThan",
"subscription_id": "00000000-0000-0000-0000-000000000000",
"resource_group_name": "Contoso",
"timestamp": "2018-02-28T10:44:10.1714014Z",
"resource_name": "diag500",
"resource_type": "Microsoft.Storage/storageAccounts",
"resource_id": "/subscriptions/1e3ff1c0-771a-4119-a03b-be82a51e232d/resourceGroups/Contoso/providers/Microsoft.Storage/storageAccounts/diag500",
"portal_link": "https://portal.azure.com/#resource//subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/Contoso/providers/Microsoft.Storage/storageAccounts/diag500"
}
Sample payload sent with Azure Monitor Common Alert Schema
{
"schemaId": "azureMonitorCommonAlertSchema",
"data": {
"essentials": {
"alertId": "/subscriptions/0000000-0000-0000-0000-000000000/providers/Microsoft.AlertsManagement/alerts/61dafc88-b4fc-4dea-b335-86081e49f000",
"alertRule": "cpu usage",
"targetResourceType": "microsoft.compute/virtualmachines",
"alertRuleID": "/subscriptions/0000000-0000-0000-0000-000000000/resourceGroups/VirtualMachine4_group/providers/microsoft.insights/metricAlerts/cpu usage",
"severity": "Sev3",
"signalType": "Metric",
"monitorCondition": "Fired",
"targetResourceGroup": "VirtualMachine4_group",
"monitoringService": "Platform",
"alertTargetIDs": [
"/subscriptions/0000000-0000-0000-0000-000000000/resourcegroups/VirtualMachine4_group/providers/microsoft.compute/virtualmachines/VirtualMachine4"
],
"configurationItems": [
"VirtualMachine4"
],
"originAlertId": "0000000-0000-0000-0000-000000000_VirtualMachine4_group_microsoft.insights_metricAlerts_cpu usage_-2033731156",
"firedDateTime": "2025-04-07T14:08:17.4045177Z",
"description": "",
"essentialsVersion": "1.0",
"alertContextVersion": "1.0",
"investigationLink": "https://portal.azure.com/#view/Microsoft_Azure_Monitoring_Alerts/Investigation.ReactView/alertId/%2fsubscriptions%2f0000000-0000-0000-0000-000000000%2fresourceGroups%2fVirtualMachine4_group%2fproviders%2fMicrosoft.AlertsManagement%2falerts%2f61dafc88-b4fc-4dea-b335-86081e49f000"
},
"alertContext": {
"properties": null,
"conditionType": "MultipleResourceMultipleMetricCriteria",
"condition": {
"windowSize": "PT5M",
"allOf": [
{
"metricName": "Percentage CPU",
"metricNamespace": "Microsoft.Compute/virtualMachines",
"operator": "GreaterThan",
"threshold": "20",
"timeAggregation": "Average",
"dimensions": ["Hello1","Hello2"],
"metricValue": 23.202,
"webTestName": null
}
],
"staticThresholdFailingPeriods": {
"numberOfEvaluationPeriods": 0,
"minFailingPeriodsToAlert": 0
},
"windowStartTime": "2025-04-07T14:00:10.212Z",
"windowEndTime": "2025-04-07T14:05:10.212Z"
}
},
"customProperties": null
}
}Payload parsed by Opsgenie (in JSON format)
{
"condition_window_size": "PT5M",
"condition_threshold": "20",
"description": "",
"originAlertId": "0000000-0000-0000-0000-000000000_VirtualMachine4_group_microsoft.insights_metricAlerts_cpu usage_-2033731156",
"condition_metric_name": "Percentage CPU",
"resolvedDateTime": "null",
"essentialsVersion": "1.0",
"condition_metric_namespace": "Microsoft.Compute/virtualMachines",
"-alertTargetIDs": ["/subscriptions/0000000-0000-0000-0000-000000000/resourcegroups/VirtualMachine4_group/providers/microsoft.compute/virtualmachines/VirtualMachine4"],
"delayIfDoesNotExists": "true",
"condition_metric_value": "23.202",
"id": "/subscriptions/0000000-0000-0000-0000-000000000/providers/Microsoft.AlertsManagement/alerts/61dafc88-b4fc-4dea-b335-86081e49f000",
"alertId": "/subscriptions/0000000-0000-0000-0000-000000000/providers/Microsoft.AlertsManagement/alerts/61dafc88-b4fc-4dea-b335-86081e49f000",
"-configurationItems": ["VirtualMachine4"],
"severity": "Sev3",
"monitorCondition": "Fired",
"condition_time_aggregation": "Average",
"monitoringService": "Platform",
"alertSource": "com.opsgenie.client.model.dto.ActionSourceCustomDto@509b3abd[domain=integration,sourceType=Azure,sourceName=tester,incomingDataId=25e2962e-b813-4fec-b54c-8d20c3548e59,sourceSubName=Create Alert,customSourceName=<null>,actorUserId=<null>]",
"condition_operator": "GreaterThan",
"condition_type": "MultipleResourceMultipleMetricCriteria",
"alertRule": "cpu usage",
"-dimensionList": ["Hello1","Hello2"],
"version": "1.0",
"alertContextVersion": "1.0",
"schemaId": "azureMonitorCommonAlertSchema",
"signalType": "Metric",
"firedDateTime": "2025-04-07T14:08:17.4045177Z",
"properties": "null",
"status": "Activated",
"dimensions": "["Hello1","Hello2"]"
}
Was this helpful?