title | description | author | manager | editor | services | documentationcenter | ms.assetid | ms.service | ms.workload | ms.tgt_pltfrm | ms.devlang | ms.topic | ms.date | ms.author |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Use Azure portal to create alerts for Azure services | Microsoft Docs |
Use the Azure portal to create Azure alerts, which can trigger notifications or automation when the conditions you specify are met. |
rboucher |
carolz |
monitoring-and-diagnostics |
monitoring-and-diagnostics |
f7457655-ced6-4102-a9dd-7ddf2265c0e2 |
monitoring-and-diagnostics |
na |
na |
na |
article |
09/23/2016 |
robb |
[!div class="op_single_selector"]
This article shows you how to set up Azure alerts using the Azure portal.
You can receive an alert based on monitoring metrics for, or events on, your Azure services.
- Metric values - The alert triggers when the value of a specified metric crosses a threshold you assign in either direction. That is, it triggers both when the condition is first met and then afterwards when that condition is no longer being met.
- Activity log events - An alert can trigger on every event, or, only when a certain number of events occur.
You can configure an alert to do the following when it triggers:
- send email notifications to the service administrator and co-administrators
- send email to additional emails that you specify.
- call a webhook
- start execution of an Azure runbook (only from the Azure portal)
You can configure and get information about alert rules using
-
In the portal, locate the resource you are interested in monitoring and select it.
-
Select Alerts or Alert rules under the MONITORING section. The text and icon may vary slightly for different resources.
-
Select the Add alert command and fill in the fields.
-
Name your alert rule, and choose a Description, which also shows in notification emails.
-
Select the Metric you want to monitor, then choose a Condition and Threshold value for the metric. Also chose the Period of time that the metric rule must be satisfied before the alert triggers. So for example, if you use the period "PT5M" and your alert looks for CPU above 80%, the alert triggers when the CPU has been consistently above 80% for 5 minutes. Once the first trigger occurs, it again triggers when the CPU stays below 80% for 5 minutes. The CPU measurement occurs every 1 minute.
-
Check Email owners... if you want administrators and co-administrators to be emailed when the alert fires.
-
If you want additional emails to receive a notification when the alert fires, add them in the Additional Administrator email(s) field. Separate multiple emails with semi-colons - [email protected];[email protected]
-
Put in a valid URI in the Webhook field if you want it called when the alert fires.
-
If you use Azure Automation, you can select a Runbook to be run when the alert fires.
-
Select OK when done to create the alert.
Within a few minutes, the alert is active and triggers as previously described.
Once you have created an alert, you can select it and:
- View a graph showing the metric threshold and the actual values from the previous day.
- Edit or delete it.
- Disable or Enable it if you want to temporarily stop or resume receiving notifications for that alert.
- Get an overview of Azure monitoring including the types of information you can collect and monitor.
- Learn more about configuring webhooks in alerts.
- Learn more about Azure Automation Runbooks.
- Get an overview of diagnostic logs and collect detailed high-frequency metrics on your service.
- Get an overview of metrics collection to make sure your service is available and responsive.