A screenshot from the Azure Logic App Designer
Why not use the VictorOps integration listed on their website?
Microsoft Azure and the incident management platform VictorOps do not have an automatically working integration at the moment. In fact, the integration they provide works with Microsoft OMS, a deprecated platform in the Azure ecosystem. This manual integration aims to include all the essential features that would include in a regular integration.
Note: This works for ALL forms of Azure alerts. You simply have to connect either alert to the action group with the logic app’s webhook (which will send the message to VictorOps).
For the time being, my fix is to use a Logic App to mold the payload into one VictorOps will accept from its REST API. Here is a summary of what we’re about to do:
Consider any alert created by the Azure Monitor. Oftentimes we would simply link this alert to an action group with a webhook that links directly to an incident management platform. For our workaround, we will instead route the webhook URL to a logic app which will handle the alert payload (because we also cannot construct a custom JSON with the current version of Azure monitor).
In a support case I opened with Azure in July 2018, a VictorOps support engineer told me that there are plans on the horizon that with deprecation/merging of OMS, custom JSON could be added to all Azure Monitor alert types/rules rendering this manual integration obsolete (but for the time being this is how we’ll handle integration).
In our logic app, whenever an HTTP request is received at our logic app’s URI, a HTTP 200 response is triggered and sent back to the original requester. In this case, the requester is the alert rule’s action group firing an HTTP request. In the logic app, we create an HTTP POST request and send it to VictorOps’ generic REST API. This POST request contains a JSON body that is written with the Logic Apps Workflow Definition Language and contains the necessary JSON fields required by the VictorOps REST endpoint. More JSON fields can be added as necessary to make the incident descriptions more readable.
Logic App (on Azure Logic Apps)
- Create a Logic App. The Logic App will serve as the central structure for the integration with VictorOps. Follow these steps:
- Create a new Logic App by clicking the Create Resource button in the top left corner of the Azure Portal. You can equivalently follow the first couple steps of this documentation.
- Name the application.
- Select an existing Resource Group.
- Create the logic app.
- From the dashboard, select the Logic App you have just created.
- From the Logic App blade, select Logic App Designer
- For the trigger condition, select “When an HTTP Request is received”
- Click New Step, select Add an Action
- Select Request Response and leave it as responding with a 200 status code (OK)
- Click New Step, select Add an Action
- Select HTTP - HTTP
- Method: POST
- URL: This can be found in your VictorOps account under Settings > Alert Behavior > Integrations > Generic REST
Headers: Content-Type application/json
- Save. Back in the Logic App Designer and under the “When an HTTP Request is Received”, the URL has now been generated. Copy this URL to the clipboard.
Note that the JSON Body will require some tweaking in the future to get the data we absolutely want in the incident. Once again, view the Logic Apps Workflow Definition Language article for more information. Most of the incident information sent to VictorOps is found in the data field.
Alerts (on Azure Monitor)
- From the left menu pane, select Monitoring » Alerts » New Alert Rule
- Define the alert however you would prefer to monitor things. For testing purposes, I find it easiest to monitor all administrative operations a condition (see Step 3)
Whenever the “Administrative Activity Log All Administrative operations” has “any” level, with “any” status and event is initiated by “
- Define the alert details with any name and description
- For the last step, select a New Action Group, this action group will fire a webhook towards
- For the action, select webhook
- For the URL of the webhook, paste the URL copied earlier from the Logic App