Rules in Azure Monitor that send notifications or trigger actions once a condition on metrics, logs or the activity log is satisfied.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Azure Monitor alerts in context, with comparison tables and the common traps.
Terms in this definition
- Azure Monitor
Observability platform for Azure that brings together metrics, logs and traces from both Azure and hybrid resources so they can be analysed and alerted on.
- Azure Functions trigger
Every function is started by exactly one thing. That thing might be a web call over HTTP, a schedule, the arrival of a blob, a message landing in a queue or a change in a database.
- Activity log
Record, held for 90 days, of control-plane operations in a subscription such as deployments and Policy events. Data-plane actions, Key Vault reads for example, are not captured.
Related terms
- Alert processing rule
Acts on already-fired Azure Monitor alerts at scale, suppressing notifications (during planned maintenance, say) or attaching action groups.
- Release gates
Automatic checks run before or after deploying in classic release pipelines, for example querying work items or Azure Monitor alerts, invoking an Azure Function or calling a REST API. YAML pipelines rely on checks for this.