Azure Monitoring Tools: Advisor, Service Health and Azure Monitor

Azure Advisor is a free service that acts like a personal consultant for your Azure environment. It continuously analyzes your resource configuration and usage, then gives you personalized recommendations to help you follow best practices and get more value from Azure. You see these recommendations in the Azure portal, often with a priority and clear steps to act on them.

Advisor organizes its guidance into five categories, which map to the pillars of a well-run cloud workload: Cost (spend less, for example by resizing or shutting down underused resources), Security (reduce vulnerabilities and threats), Reliability (improve the availability and resilience of your applications), Operational excellence (improve process and deployment efficiency), and Performance (speed up and scale your applications).

The key idea for the exam is that Advisor gives recommendations to optimize your existing resources across those five areas. It does not tell you whether Azure is broken, and it is not a live monitoring dashboard. If a scenario asks for personalized recommendations across the five pillars, such as advice to resize an underused virtual machine to save money, the answer is Azure Advisor.

Azure Service Health answers a specific and important question: is a problem with Azure itself affecting my resources right now? Azure runs across many regions and services, and occasionally there are outages or maintenance windows. Service Health gives you a personalized view of health events that are relevant to the services and regions you actually use, rather than a generic global report.

It covers three kinds of events: service issues (active outages in Azure that may be impacting you right now), planned maintenance (upcoming work that could affect your resources, so you can prepare), and health advisories (changes that need your attention, such as a feature being retired or a configuration you should update).

It helps to contrast Service Health with the public Azure status page, a general web page showing the health of Azure services worldwide for everyone. That page is not tailored to you. Service Health narrows things down to your subscriptions and resources, and you can set up alerts so you are notified when a relevant event occurs. For the exam, remember: to find out whether an Azure outage or maintenance is affecting your services, use Azure Service Health.

Azure Monitor is the comprehensive, full-stack monitoring platform in Azure. While Advisor gives advice and Service Health reports on Azure's own status, Azure Monitor is where you collect, analyze, and act on telemetry from your own applications and infrastructure. Telemetry is the data your resources emit about how they are behaving.

Azure Monitor gathers two broad kinds of data. Metrics are numeric values sampled over time, such as CPU percentage or request counts, useful for spotting trends and current health. Logs are detailed records of events and activity that you can search and analyze in depth. Almost everything in Azure feeds data into Azure Monitor, giving you one place to understand the state of your whole environment, from virtual machines and databases to networks and applications.

Because Azure Monitor is a platform, it is best understood through its main components, covered in the next sections: Log Analytics for querying log data, Azure Monitor alerts for being notified when something needs attention, and Application Insights for monitoring the performance of your applications. Think of Azure Monitor as the umbrella, and these three as the tools underneath it that do the specialized work.

Log Analytics is the tool within Azure Monitor for querying and analyzing log data. The logs collected by Azure Monitor are stored in a Log Analytics workspace, and Log Analytics is where you write queries against that data to answer questions and dig into what happened.

Queries are written in Kusto Query Language (KQL), a read-focused language designed for exploring large volumes of log data quickly. With KQL you can filter, sort, summarize, and chart your logs, for example, to count how many errors a service produced in the last hour, or to trace the sequence of events that led up to a failure. You do not need to master KQL for the AZ-900 exam; you just need to know that Log Analytics is where you query logs, using KQL.

Log Analytics is powerful because it brings data from many sources into one place, letting you correlate signals that would otherwise be scattered. If an exam scenario mentions querying or analyzing collected log data to investigate an issue, the tool is Log Analytics, which is part of Azure Monitor. It turns raw logs into answers you can search and visualize.

Azure Monitor alerts let you be notified and take action automatically when something in your environment meets a condition you care about, so you do not have to sit and watch dashboards. You define a rule that says what to watch and when to fire, for example, when a virtual machine's CPU stays above 90 percent, or when a specific error appears in the logs.

When the condition is met, the alert triggers an action. Actions are grouped into action groups, which define what happens next: send an email or SMS, push a mobile notification, call a webhook, or kick off automation to respond. This means alerts can both tell you about a problem and help act on it.

Alerts can be based on the metrics or the logs that Azure Monitor collects, so they work across both numeric thresholds and log queries. The value is that you catch issues early, ideally before your users notice, and respond consistently every time. For the exam, remember the purpose plainly: Azure Monitor alerts notify you, or trigger an action, when a defined condition occurs. They are the proactive layer on top of the data that Azure Monitor already gathers.

Application Insights is the part of Azure Monitor focused on application performance monitoring (APM), that is, understanding how your web applications and services behave from the inside. You add it to your app, and it automatically collects telemetry about how the application is running.

Application Insights tracks things like response times (how fast requests are served), failure and error rates (which requests are failing and why), request volumes and dependencies (how much traffic you get and how calls to databases or other services are performing), and usage (how people move through your app). It presents this as charts and detailed diagnostics, so you can pinpoint a slow page or a failing operation.

The classic use case is performance and reliability of a live web app. If your checkout page suddenly feels slow, Application Insights helps you see exactly which requests are slow and where the time is going. For the exam, connect the trigger words directly: to monitor a web application's performance, availability, and failures, the answer is Application Insights, a feature of Azure Monitor. It is about your application, not Azure's own status.

The fastest way to answer exam questions here is to know which tool answers which question. Advisor is advisory, Service Health is about Azure's status affecting you, and Azure Monitor is about watching your own applications and infrastructure in detail. They are complementary, not competing.

Keep the scope in mind for the exam. Anything about spending, tagging, or the pricing calculator is cost management, and governance features such as Azure Policy and resource locks are separate topics. The tools you use to deploy and manage resources, the portal, CLI, PowerShell, Arc, and templates, belong to another Domain 3 topic. This lesson is strictly about monitoring, so match the scenario to the tool whose core question fits.

Suppose you run an online store on Azure, and three different things happen in one week. Each one points to a different monitoring tool.

First, customers complain that the product page loads slowly. You open Application Insights and look at response times and failures for your web app. It shows that one type of request, a call to your database, is taking far longer than the rest, so you know exactly where to focus. That is application performance monitoring in action.

Second, you notice sporadic errors and want to confirm a pattern. You use Log Analytics to run a KQL query over your collected logs, counting errors by hour, and you set an Azure Monitor alert so you are emailed if the error rate spikes again. Now you will be told the moment it recurs.

Third, several unrelated services in one region briefly misbehave. You check Azure Service Health, which shows an active service issue in that region affecting your resources, reassuring you it is Azure's problem, not yours. Later, Azure Advisor recommends resizing an underused virtual machine to cut costs. Three signals, three tools, each doing its own job.