This chapter covers Azure Monitor, Azure's central platform for collecting and acting on monitoring data. AZ-900 tests this under objective 3.3, "Describe monitoring tools in Azure."
Jump to a section
A simple way to picture Azure Monitor
A large building doesn't rely on someone manually checking every room for problems — it has a central system collecting signals from smoke detectors, temperature sensors, and security cameras throughout the building, giving facilities staff a unified view and the ability to set up alerts when something needs attention. Azure Monitor works the same way for cloud resources: it collects data from across an organization's Azure resources — performance metrics, logs, and other signals — into a central place, providing visibility and enabling alerts when something needs attention.
What Azure Monitor does
Azure Monitor collects, analyzes, and acts on telemetry data — metrics and logs — from Azure resources (and, with appropriate configuration, non-Azure resources too), giving organizations visibility into the performance and health of their environment.
Metrics and logs
Azure Monitor generally works with two kinds of data: metrics, which are numerical values measured over time (like CPU usage or response time), and logs, which are structured records of events (like an error message or an audit trail entry). Together, they provide both a quantitative view of performance and a detailed record of what actually happened.
Alerts
Based on collected metrics or logs, Azure Monitor can trigger alerts when specific conditions are met — for example, notifying a team when CPU usage on a virtual machine exceeds a defined threshold, or when a specific error appears in application logs.
Dashboards and visualization
Azure Monitor supports visualizing collected data through dashboards, giving teams an at-a-glance view of their environment's health and performance, rather than needing to review raw data manually.
How it relates to other monitoring-adjacent services
Azure Monitor is the broad, central platform; more specific tools like Azure Service Health (covered in the next chapter) and Azure Advisor (covered later) build on or complement it for more specific purposes.
Collect metrics and logs
Azure Monitor collects telemetry — metrics (numerical measurements over time) and logs (structured event records) — from Azure resources.
Analyze and visualize the data
Collected data can be visualized through dashboards, giving teams an accessible view of their environment's performance and health.
Configure alerts
Alerts are configured to trigger based on specific conditions in the collected metrics or logs, notifying relevant people when something needs attention.
Take action based on insights
The visibility Azure Monitor provides supports both reactive troubleshooting (responding to an alert) and proactive optimization (spotting trends before they become problems).
A team monitors their web application's response times using Azure Monitor, configuring an alert to notify them if response times exceed an acceptable threshold, allowing them to investigate and respond before customers are significantly affected.
A separate team uses Azure Monitor's log data to investigate the root cause of an intermittent error after receiving customer complaints, using the detailed event records to trace exactly what happened, rather than only having access to a simple numerical metric that wouldn't explain the underlying cause.
Objective 3.3 expects candidates to understand Azure Monitor's general role in collecting metrics and logs, and enabling alerts and visualization — implementation-level querying detail isn't required at this level.
A common wrong answer is confusing metrics and logs — metrics are numerical measurements over time; logs are structured records of specific events. Another common trap is assuming Azure Monitor only works with Azure resources — it can also collect data from non-Azure resources with appropriate configuration.
Stable terms: Azure Monitor, metrics, logs, alerts. Recognizing Azure Monitor as the central, broad monitoring platform that other tools build on is the core exam-relevant idea.
Memory trick: metrics = numbers over time (how much, how fast). Logs = detailed records of specific events (what exactly happened). Azure Monitor collects both and can alert on either.
Azure Monitor collects, analyzes, and acts on metrics and logs from Azure (and, with configuration, non-Azure) resources.
Metrics are numerical measurements over time; logs are structured records of specific events.
Azure Monitor supports alerts, triggered when defined conditions are met in collected data.
Azure Monitor is the broad, central monitoring platform that more specific tools like Service Health and Advisor build on.
These come up on the exam all the time. Here's how to tell them apart.
Metrics
Numerical values measured over time
Example: CPU usage, response time
Good for spotting trends and thresholds
Logs
Structured records of specific events
Example: an error message, an audit entry
Good for investigating exactly what happened
Mistake
Metrics and logs are the same kind of data.
Correct
Metrics are numerical measurements over time (like CPU usage); logs are structured records of specific events (like an error message). They serve different purposes and are both collected by Azure Monitor.
Mistake
Azure Monitor only works with Azure resources.
Correct
With appropriate configuration, Azure Monitor can also collect data from non-Azure and on-premises resources, not just resources running in Azure itself.
Mistake
Alerts in Azure Monitor require someone to manually check dashboards constantly.
Correct
Alerts can be configured to proactively notify relevant people when a defined condition is met, rather than requiring continuous manual monitoring of dashboards.
It's Azure's central platform for collecting, analyzing, and acting on monitoring data — metrics and logs — from Azure resources, giving organizations visibility into performance and health, along with the ability to configure alerts.
Metrics are numerical values measured over time, like CPU usage or response time — good for spotting trends. Logs are structured records of specific events, like an error message — good for investigating exactly what happened during an incident.
No — with appropriate configuration, it can also collect data from non-Azure and on-premises resources, giving broader visibility beyond just resources running in Azure.
You've just covered Azure Monitor — now see how well it sticks with free AZ-900 practice questions. Full explanations included, no account needed.
Done with this chapter?