What is Azure Monitor? A plain-English explainer
Azure Monitor is Azure’s observability platform: a single service that collects metrics and logs from almost everything running in an Azure subscription, then turns that data into alerts, dashboards and deeper diagnostics. Rather than each resource — a virtual machine, a database, a web app — reporting to a different place, Azure Monitor is the common collection point, so an administrator has one service to open when something needs investigating. It also folds in Application Insights, its application-performance-monitoring layer, so the same platform covers infrastructure health and application behaviour. Because “is anything wrong, and how do I find out” is a question every Azure environment eventually asks, Azure Monitor shows up early in Azure certification study. Here is what it actually collects, what you do with that data, and how it compares across clouds.
What observability is, and where Azure Monitor sits
Observability is the broader concept: being able to tell what a system is doing, and why, from the data it produces — typically metrics (numbers over time, like CPU usage), logs (structured or free-text records of events) and traces (the path a single request takes through a system). Our what-is-observability explainer covers those building blocks in full.
Azure Monitor is Azure’s implementation of that idea. It is not one narrow tool but a platform: metrics flow into it automatically from most Azure resources, logs are stored and queried through its Log Analytics component, and both feed the alerts and dashboards layered on top. You do not choose between “Azure Monitor or something else” for basic resource health — it is switched on by default and expands from there.
What Azure Monitor actually does
Broadly, Azure Monitor’s job splits into a few connected parts:
- Metrics — lightweight, numerical data (CPU, memory, request counts) collected automatically from most Azure resources and viewable as near-real-time charts.
- Logs, via Log Analytics — a queryable store for structured log data, searched with the Kusto Query Language (KQL), for questions metrics alone can’t answer.
- Alerts — rules that watch metrics or log queries and notify someone, or trigger an automated action, when a condition is met.
- Dashboards and workbooks — visual summaries built from metrics and log queries, so a team can see health at a glance rather than querying each time.
- Application Insights — the application-performance-monitoring piece, tracking requests, dependencies, exceptions and performance inside an application’s own code, not just the infrastructure underneath it.
When you would reach for Azure Monitor
In practice, Azure Monitor is less a tool you deliberately “use” and more a service you configure and then consult: setting up alerts before something breaks, building a dashboard a team checks each morning, or querying logs after an incident to work out what happened and when. Application Insights specifically earns its keep once you need to see inside an application — which dependency call is slow, which exception is spiking — rather than just knowing the virtual machine underneath it is healthy.
It is also the foundation other Azure services build on: autoscaling rules, many security tools, and third-party monitoring integrations all read from the same metrics and logs Azure Monitor collects, rather than each maintaining a separate pipeline.
The Azure counterpart to CloudWatch
Every major cloud provider ships an equivalent platform, because “collect telemetry, alert on it, visualise it” is a need every cloud customer has. Azure Monitor is Azure’s counterpart to Amazon CloudWatch on AWS, and Google Cloud’s operations suite plays the same role there. The concepts transfer directly — metrics, logs, alerts, dashboards — even though the specific query languages and interfaces (KQL and Log Analytics on Azure, CloudWatch Logs Insights on AWS) differ.
How you pay for it, without the numbers
Azure Monitor follows the consumption model common across observability tooling: you are billed for what you actually collect and retain — the volume of log data ingested and stored, and the number of alert rules and notifications — rather than a flat platform fee. Exact rates and free allowances change over time, so this article deliberately avoids listing them; check Microsoft’s official Azure Monitor pricing page for current detail. The concept worth keeping is that what you choose to log, and for how long you keep it, is a real cost decision, not just a technical one.
Where Azure Monitor appears in certification study
Azure Monitor is core content on Azure’s administration path. Azure Administrator Associate (AZ-104) tests configuring metrics, alerts and Log Analytics workspaces directly, since monitoring and troubleshooting resources is a named exam skill. Azure Fundamentals (AZ-900) introduces it at a conceptual level, as part of Azure’s management and governance tooling. It is also useful background for cloud operations certifications on other providers, since the underlying idea — one platform, telemetry in, alerts and dashboards out — is the same skill wearing a different name.
This article covers what Azure Monitor is and why it matters — writing KQL queries, configuring specific alert conditions and setting up Application Insights belong in the syllabus itself, which our /revision study library breaks down lesson by lesson for these certifications.
Original practice questions, timed mock exams and revision notes. No card, nothing to pay.