Azure Monitor integration
Bring Azure alert rules into HowlOps as incidents, so Azure workloads are covered by the same on-call flow as everything else.
What this brings you
If part of your stack runs on Azure, its metric, log, activity-log, and Prometheus-based alert rules can all feed straight into HowlOps as incidents. That means Azure alerts go through the same escalation policy, the same status page, and the same incident history as the rest of your monitoring, instead of living only in the Azure portal.
Setup
- In HowlOps, open Integrations in the sidebar (the Integration Hub).
- Under Bring alerts into HowlOps, click the Azure Monitor source card, then Generate endpoint to get a token-scoped webhook URL.
- In Azure, open the alert rule's Action Groups and add (or edit) a Webhook action with the endpoint from step 2 as its URI.
- On that action, set Enable the common alert schema to Yes. HowlOps parses the common alert schema's envelope, which Azure only sends once this is enabled.
- Trigger a test alert and confirm the incident appears in HowlOps.
A monitorCondition of Resolved in the Azure payload closes the matching HowlOps incident. Azure's severity (Sev0 through Sev4) maps to HowlOps severity: Sev0/Sev1 become critical, Sev2 becomes warning, and Sev3/Sev4 become info.
See also
- Integrations reference for the endpoint format and severity mapping details.
- Incidents & severities for how an inbound alert becomes an incident.
Was this page helpful?