Microsoft Azure Monitor
Microsoft Azure Monitor collects and analyzes critical event data to maximize the performance and uptime of your digital services in Azure Cloud. Combined with xMatters, the Azure Monitor integration monitors on-premise and cloud-based environments and turns critical event data into actionable notifications for on-call responders to tackle any issues that occur.
This workflow lets you send actionable alerts to on-call resources when xMatters gets a signal from Microsoft Azure Monitor. Responders can initiate an incident with the press of a button, or you can build on the flow to perform automated resolution tasks.
How it works
When an alert is generated in Microsoft Azure Monitor, it sends a JSON-formatted webhook to xMatters, based on the user-defined alert rules. An HTTP trigger in xMatters parses the webhook and initiates a flow. The webook includes essential alert data that is included in notifications sent to users, and details about the origin of the alert that you can use to enrich the notifications or use when building automated tasks.
- Go to the Workflows Templates page and click the Microsoft Azure Monitor tile.
- On the Install Workflow dialog box, give the workflow a name (this must be unique in your instance) and add an optional description.
- You can edit these later, if needed.
- Click Install.
- After the workflow installs, the screen shows next steps as well an installation log. The installation log gives you additional information about the installation, such as if you have languages in your instance that aren't configured for the messages in the workflow.
- Select the authentication option you want to use.
- Copy the trigger URL — you’ll use this to configure a webhook in Microsoft Azure Monitor.
- The trigger URL includes the recipients parameter, which specifies who should be notified. By default, this parameter is set to notify you, the logged in user, but you can set it to target any user or group you want.
- Click Done.
Configure Azure Monitor to send requests to the trigger URL
To have Azure Monitor send alerts to the flow trigger, you need to configure a webhook for an action group and set it to use the trigger URL.
- In Azure, go to Alerts > Manage Actions > Add action group (or navigate to an existing action group you want to add the xMatters alert to).
- On the Basics tab, configure the action group settings (subscription, resource group, name, and display name).
- Go to the Actions tab, add a new action, and set Action type to Webhook.
- Give the webhook a name (for example, xMatters Antares for a webhook that alerts xMatters about issues with the Antares service).
- In Details, copy the trigger URL from the trigger into the URL field.
- Add the target names of any recipients you want xMatters to notify when the alert fires.
- For example, if you want to notify Emma Pearson and the on-call members in the group responsible for the Antares service, you'd add ?recipients=epearson,antares to the URL. You must URL-encode any special characters or spaces in the target names.
- Make sure to set Enable the common alert schema to Yes.
- The settings on the Notifications and Tags tabs are optional.
- Click Review + create. If you're happy with the settings, click Create.
You're ready to use the webhook to trigger automated flows, including steps such as sending alerts and initiating incidents, though we always recommend testing before putting things into use.
The trigger expects the recipients in the trigger URL. When you copy the URL from xMatters, it includes the recipients parameter: recipients=<yourname>. Of course, you don’t want to receive all the alerts.
To change the recipients for alerts from this webhook, swap out your name for the people or groups you want to target. For example, to target the Antares service team and the Database Admins add recipients=antaresteam,dbadmins to the trigger URL. Remember to URL-encode any special characters in your group names.
When an alert rule you’ve set to use the action group fires, it sends a signal to xMatters, which creates an event and notifies the individual or the on-call members of the groups you set as recipients in the webhook URL.
When the trigger receives a signal saying the issue is resolved, it automatically terminates related events in xMatters. Some types of Azure Monitor alerts (for example, resource health) don’t send a signal when they resolve, which means xMatterscan’t terminate those events.
The person responding to the notification has the following response options:
- Acknowledge: Acknowledges the notifications and stops escalations.
- Escalate: Immediately escalates the event to the next on-call resolver in a targeted group.
- Close: Ends the xMatters event and stops notifying all targeted recipients.
- Initiate Incident: Initiates an incident in xMatters.
Now that you've installed the workflow, you can use it as-is, or customize it to suit your needs better. Here are some examples of things you can add to the workflow to customize it: