Chapter 5 · Monitor and Maintain Resources·v2.0.0·Updated 6/28/2026·~9 min

What's changed: Deepened AZ-104 Chapter 5 to Associate depth (tables, scenarios, FAQ, traps; localized figures)

5.1Monitoring with Azure Monitor

Key points

Understand monitoring basics: Azure Monitor metrics and logs (Log Analytics / KQL), alerts and actions, and connection diagnostics with Network Watcher.

Stable operations require monitoring—knowing what is happening now. Azure Monitor is the monitoring platform, collecting metrics and logs.

5.1.1Metrics, logs, and alerts

Diagram of Azure Monitor data flow: it collects metrics (numeric) and logs (Log Analytics) from resources (VMs, apps, network) and feeds alerts and actions (email/autoscale) and dashboards, noting metrics = real-time numbers, logs = records queryable with KQL. — Azure Monitor data flow

Metrics: numeric time-series like CPU usage; near real-time.
Logs: records of events/diagnostics, collected in Log Analytics and analyzed with KQL.
Alerts: fire on conditions like threshold breaches and run actions like email or autoscale.
Network Watcher: performs network diagnostics like connection checks and packet capture.

Exam point

Common on AZ-104: numeric time-series = metrics, log aggregation/analysis = Log Analytics + KQL, notify/auto-respond on conditions = alerts + action groups, network diagnostics = Network Watcher.

Continue reading — free sign-up

You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.

Get started free Log in