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.
Read more: Microsoft Learn
In the Ultra Transcenders books
AZ-104AZ-700SC-500AI-300AZ-900AI-200DP-750SC-200AZ-400AZ-802DP-600
Each book explains Azure Monitor in context, with comparison tables and the common traps.
Related terms
- Action group
Azure Monitor's reusable definition of contacts and automated responses for when an alert or budget fires. Contacts can be reached by email, SMS, push or voice; responses include webhooks, Functions, Logic Apps and Automation runbooks. Budgets alone can only send notifications.
- Action groups
Sets of notification and automation targets in Azure Monitor that an alert calls when it fires. Detecting the problem is the alert rule's job, not theirs.
- Alert rule
Azure Monitor definition made up of a scope naming the target resources, a condition setting the signal and logic, and optionally action groups. A separate rule is needed for every signal that has different recipients.
- Application Insights
APM service within Azure Monitor providing application telemetry, availability tests, usage analytics and Application Map. Data from workspace-based instances lives in Log Analytics.
- Autoscale
Azure Monitor capability that adds or removes instances on a schedule or once a metric rule has been true for its full duration. The maximum instance count merely sets a ceiling and never triggers scaling itself.
- Azure Monitor alerts
Rules in Azure Monitor that send notifications or trigger actions once a condition on metrics, logs or the activity log is satisfied.
- Azure Monitor Logs
Within Azure Monitor, the store for log data: records of logs and performance counters are kept in Log Analytics workspaces, where KQL queries retrieve them.
- Azure Monitor managed service for Prometheus
Metrics in Prometheus format land in Azure Monitor workspaces rather than Log Analytics ones, with Microsoft running the whole service.