Study guide
2.3 Azure Monitor Metrics & Alerting Design
Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Orientation
1.1 AZ-305 Current Exam Facts & Format 1.2 Candidate Profile, Prerequisites & the AZ-104 Requirement 1.3 Skills Outline, Domain Weights & How to Use This Guide
2 Chapter 2: Logging, Monitoring & Diagnostics Design
2.1 Logging Solution Design 2.2 Log Routing Design 2.3 Azure Monitor Metrics & Alerting Design 2.4 Application Insights & Diagnostic Monitoring Design
3 Chapter 3: Authentication & Authorization Design
3.1 Authentication Solution Design 3.2 Identity Management Design 3.3 Authorization for Azure Resources 3.4 Authorization for On-Premises Resources 3.5 Secrets, Certificates & Key Management Design
4 Chapter 4: Governance, Compliance & Identity Governance Design
4.1 Management Group & Subscription Hierarchy Design 4.2 Resource Group Organization & Tagging Strategy Design 4.3 Compliance Management Design 4.4 Identity Governance Design
5 Chapter 5: Relational Data Storage Design
5.1 Relational Data Storage Selection 5.2 Database Service & Compute Tier Design 5.3 Database Scalability Design 5.4 Relational Data Protection Design
6 Chapter 6: Semi-Structured & Unstructured Data Storage Design
6.1 Semi-Structured Data Storage Design 6.2 Unstructured Data Storage Design 6.3 Storage Tier & Cost-Performance Trade-off Design 6.4 Unstructured Data Protection & Durability Design
7 Chapter 7: Data Integration & Analytics Design
7.1 Data Integration Pipeline Design 7.2 Event-Based & Real-Time Data Integration Design 7.3 Data Analytics Platform Design
8 Chapter 8: Backup & Disaster Recovery Design
8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO 8.2 Azure Site Recovery Architecture for Hybrid Workloads 8.3 Compute Backup & Recovery Design 8.4 Database Backup & Recovery Design 8.5 Unstructured Data Backup & Recovery Design
9 Chapter 9: High Availability Design
9.1 Compute High Availability: Availability Sets & Availability Zones 9.2 Compute High Availability: Load Balancing & VM Scale Set Design 9.3 Relational Data High Availability Design 9.4 Semi-Structured & Unstructured Data High Availability Design
10 Chapter 10: Compute Solution Design
10.1 Compute Requirements Analysis & Virtual Machine-Based Solution Design 10.2 Container-Based Solution Design (AKS, Container Apps, Azure Container Instances) 10.3 Serverless-Based Solution Design (Azure Functions, Logic Apps) 10.4 Batch Processing Solution Design (Azure Batch, HPC Workloads)
11 Chapter 11: Application Architecture Design
11.1 Messaging Architecture Design (Service Bus, Queue Storage) 11.2 Event-Driven Architecture Design (Event Grid, Event Hub) 11.3 API Integration & Application Caching Design (API Management, Azure Cache for Redis, CDN) 11.4 Application Configuration Management & Automated Deployment Design (App Configuration, DevOps Pipelines, Deployment Slots)
12 Chapter 12: Migration Design
12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation 12.2 IaaS & PaaS Workload Migration Design 12.3 Database Migration Design (Data Migration Service, Database Migration Assistant) 12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)
13 Chapter 13: Network Solution Design
13.1 Internet Connectivity Design 13.2 Hybrid Connectivity Design 13.3 Network Security Optimization Design 13.4 Network Performance Optimization & Load-Balancing/Routing Design
14 Chapter 14: Final Review, Exam Strategy & Career Path
14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions 14.2 Common AZ-305 Decision Traps 14.3 Final Study Plan & Practice Assessment Strategy 14.4 After AZ-305: Retake Policy, Renewal & Career Path
2.3 Azure Monitor Metrics & Alerting Design
Key Takeaways Explain This Topic AI
Match alert type to signal: metric alerts for fast numeric thresholds, log search alerts for KQL correlation, activity log alerts for control-plane/service-health events, smart detection for automatic Application Insights anomalies
Stateful alerts (metric, log search) suppress repeat notifications until resolved; stateless activity log alerts fire every time the condition is met
Metric alerts resolve after 3 consecutive checks below threshold; log search alert resolution timing depends on the rule's evaluation frequency
Action groups separate notification channels (email/SMS/voice/push) from automated actions (Automation runbooks, Azure Functions, Logic Apps, ITSM, webhooks, Event Hubs)
Scale alerting with one multi-resource metric rule per region/type or workspace-wide log search alerts split by resourceId, instead of duplicating per-resource rules
Last updated: July 2026
Why This Topic Matters on AZ-305
Recommend a monitoring solution is a single official Microsoft bullet broad enough that this guide splits it into two sections; this section covers the metrics and alerting half. Detecting a problem is only useful if someone gets notified fast enough to act — AZ-305 scenarios routinely test whether you picked the right alert signal type , the right evaluation configuration , and the right notification/automation mechanism for a given business requirement (for example, "notify the on-call engineer within five minutes" versus "open a ticket automatically").
Core Concepts: Alert Rules, Alerts, and Action Groups
An alert rule combines three things: the resource(s) monitored, the signal/data source, and the condition that must be met. When conditions are met, the rule fires an alert , which triggers an associated action group . Alerts in the portal are retained for 30 days .
Azure Monitor supports several alert types , and choosing the right one is the most heavily tested part of this topic:
Alert type Signal source Best for
Metric alerts Platform metrics, custom metrics, Application Insights metrics, or log-converted metrics Fast, near-real-time thresholds (CPU%, queue depth); supports multiple conditions and dynamic thresholds (ML-derived, adapts to seasonal/noisy baselines instead of a fixed number)
Log search alerts A scheduled KQL query against a Log Analytics workspace Complex correlation logic across multiple tables/resources that a simple metric can't express
Simple log search alerts KQL, but evaluates each row individually rather than aggregating over a window Fastest possible log-based alerting, minimal KQL aggregation skill required
Activity log alerts A new Activity Log event matching defined conditions Control-plane changes; Service Health and Resource Health alerts are specialized activity log alerts for Microsoft-side incidents vs. your own resource's health
Smart detection alerts Automatic Application Insights anomaly detection Performance and failure anomalies in a web app, with no rule authoring required
Alert State Behavior
Alerts are either stateful or stateless , and the exam expects you to reason about when notifications repeat and when an alert is considered resolved :
Stateless (all Activity Log alerts): fires every time the condition is met, with no concept of "already notified."
Stateful (metric and log search alerts): fires once, stays in a fired state, and suppresses repeat notifications until the underlying condition clears and the rule marks it resolved .
A metric alert resolves after the condition is not met for three consecutive evaluation checks .
A log search alert resolves based on its frequency: at 1-minute frequency, after 10 minutes of the condition not being met; at 5-15 minute frequency, after three frequency periods; at 15 minutes-11 hours, after two frequency periods.
Exam trap : for a stateless metric alert configured with a frequency under 5 minutes, a repeat notification can arrive 1-6 minutes after the condition continues to be true; at 5 minutes or more, expect a notification somewhere between the configured frequency and double that frequency (a 15-minute rule can take up to 30 minutes to notify again).
Action Groups: Notifications and Automation
An action group is a reusable bundle of response actions triggered by one or more alert rules. It supports two categories:
Notifications : email, SMS, voice call, push notification (via the Azure mobile app).
Actions : Automation runbooks, Azure Functions, ITSM (IT Service Management) connector incidents, Logic Apps, secure webhooks, plain webhooks, and Event Hubs.
Alert processing rules sit on top of action groups and let you modify triggered alerts in flight — for example, suppressing notifications for a defined maintenance window, or adding an extra action group temporarily — without editing every underlying alert rule.
Alerting at Scale
Three patterns matter for enterprise-scale AZ-305 designs:
One metric alert rule across many resources of the same type in the same Azure region (for example, one rule watching CPU across an entire VM Scale Set fleet), with a separate notification fired per resource.
Workspace-wide log search alerts that can span resources across subscriptions and regions, as long as they send data to the same Log Analytics workspace; use splitting by dimensions on the resourceId column to get one alert per resource instead of one alert for the whole query.
Azure Policy-driven alerting , deploying the same alert rule definition across many subscriptions at once (for example, via the Azure Monitor Baseline Alerts pattern) — trades easy at-scale rollout for the ongoing maintenance overhead of a larger managed rule set.
Microsoft also ships recommended out-of-the-box alert rules for VMs, AKS clusters, and Log Analytics workspaces, which can shortcut initial designs before custom tuning.
Scenario Walkthrough
An application team needs to know within minutes if any VM in a 50-instance scale set exceeds 85% CPU for five sustained minutes, and they want an Automation runbook to automatically scale out the set, plus an email to the on-call engineer. The design uses one metric alert rule targeting the scale set as a whole (satisfying "one resource type, one region"), a static threshold of 85% over a 5-minute aggregation window, and an action group combining an Automation runbook action (auto-scale) with an email notification — a single alert rule and a single action group cover the entire fleet instead of 50 separate rules.
Key Takeaways
Match the alert type to the signal: metric alerts for fast numeric thresholds, log search alerts for KQL-driven correlation, activity log alerts for control-plane/service-health events, smart detection for automatic Application Insights anomalies.
Stateful alerts (metric, log search) suppress repeat notifications until resolved; stateless activity log alerts fire every time.
Action groups separate notification channels (email/SMS/voice/push) from automated actions (runbooks, Functions, Logic Apps, ITSM, webhooks); alert processing rules modify in-flight behavior like maintenance-window suppression.
Use dynamic thresholds for noisy or seasonal metrics instead of hand-tuned static numbers.
Scale alerting with one multi-resource metric rule per region/type, or workspace-wide log search alerts split by resourceId , rather than duplicating rules per resource.