Azure Metric Alerts Integration
Azure Metric Alerts — Webhook Integration
Azure Monitor lets you fire alerts when any resource metric crosses a threshold — CPU usage, storage capacity, request latency, whatever you're tracking. Those alerts can hit a webhook endpoint directly via Action Groups, which is how we get them into the on-call platform.
This guide walks through setting up a Storage Account metric alert as an example. The same steps apply to any other Azure resource type.
1. Create a Storage Account (if you don't have one)
You need at least one Azure resource to attach a metric alert to. A Storage Account works well for testing — it's free to create and always has measurable metrics.
Go to Azure Portal → search Storage accounts → + Create. Fill in the basics (subscription, resource group, name, region) and click through to Review + create.
Hit Create. Once the deployment finishes you'll see this:
Click Go to resource to open the storage account.
2. Create the alert rule
From the storage account overview, go to Monitor → Alerts in the left panel, then + Create → Alert rule. On the Scope tab, click Select scope — a panel slides in on the right. Find your storage account in the list, check it, and hit Apply.
3. Set the condition
Switch to the Condition tab. Click Select a signal — a search panel opens. Type used and select Used capacity from the results.
On the condition configuration screen, set the threshold to whatever makes sense for your alert. For a quick test, Greater than 0 bytes works fine since any data in the account will trigger it.
Click Next: Actions.
4. Create the action group
On the Actions tab, select Use action groups, then + Create action group. Give it a name — something like OnCall-Webhook-Group — and set a short display name.
Click through to the Actions tab within the action group form. Set Action type to Webhook, give it a name like TriggerWebhook, and paste your on-call platform webhook URL into the URI field. Make sure Enable the common alert schema is set to Yes — this standardizes the payload format across all Azure alert types.
Hit OK, then Review + create → Create.
Back in the alert rule form, you'll see a panel to select from existing action groups. Pick OnCall-Webhook-Group and click Select.
5. Name the alert rule
On the Details tab, give the alert rule a descriptive name. Set the severity level to match what this alert means for your environment.
Click Review + create → Create.
6. Verify the action group
To confirm the webhook URL is correctly set, go to Monitor → Alerts → Action groups and open OnCall-Webhook-Group. The Actions section should show the webhook entry with your URL.
That's it. When the metric condition is met, Azure will POST the alert payload to your webhook URL and the on-call platform will create an alert automatically.
Field mappings
Azure Metric alerts use the Common Alert Schema. The platform reads the following fields:
data.essentials.alertId
Fingerprint — ties together fired and resolved events for the same alert
data.essentials.monitorCondition
Fired → ALERT, Resolved → RESOLVE
data.essentials.severity
Priority
data.essentials.alertRule
Alert title
Severity to priority mapping:
Sev0
CRITICAL
Sev1
HIGH
Sev2
MEDIUM
Sev3
LOW
Sev4
LOW
Will alerts resolve automatically? Yes — when the metric condition clears, Azure fires another webhook with monitorCondition: Resolved and the platform closes the alert.
Last updated
Was this helpful?