Why Monitoring Matters
In the cloud, workloads are dynamic and distributed. Unlike on-prem systems where admins have direct access to physical servers, Azure requires proactive monitoring to detect issues, measure performance, and ensure compliance with SLAs.
Azure Monitor provides the foundation for observability across applications, infrastructure, and services.
Azure Monitor Overview
Definition:
A unified monitoring service that collects, analyzes, and acts on telemetry data from Azure, on-premises, and hybrid resources.
Core Components:
-
Metrics
-
Numerical, real-time performance data (CPU %, memory, IOPS).
-
Collected at 1-minute granularity (faster for premium tiers).
-
-
Logs (Activity Logs & Diagnostic Logs)
-
Activity Logs → what happened at subscription level (who created/deleted a VM).
-
Resource Logs (Diagnostic Logs) → detailed data from specific resources (VM events, network flows).
-
Stored in Log Analytics Workspace.
-
-
Data Sources
-
Azure resources (VMs, DBs, storage).
-
Applications (via App Insights).
-
On-prem/hybrid resources (via Azure Arc).
-
Monitoring Flow
-
Data Collection → Metrics + Logs from resources.
-
Data Storage → Log Analytics Workspace.
-
Analysis → KQL queries, dashboards.
-
Response → Alerts, Automation, Playbooks.
Example Enterprise Scenario
A retail company wants to monitor:
-
VM performance (CPU/memory).
-
Network traffic spikes.
-
Who deleted resources in subscription.
Correct design:
-
Use Azure Monitor Metrics for VM CPU/memory.
-
Enable NSG flow logs for network traffic.
-
Use Activity Logs to track resource deletion events.
Confusion Buster
-
Metrics vs Logs
-
Metrics = numbers, near real-time (performance).
-
Logs = detailed records, contextual (who/what/why).
-
-
Activity Logs vs Diagnostic Logs
-
Activity Logs = control-plane operations (resource creation/deletion).
-
Diagnostic Logs = data-plane operations (inside resource).
-
-
Azure Monitor vs Log Analytics
-
Monitor = umbrella service.
-
Log Analytics = query engine inside Monitor.
-
Exam Tips
-
“Which service collects telemetry data for Azure resources?” → Azure Monitor.
-
“Which captures VM CPU utilization in near real time?” → Metrics.
-
“Which log tracks resource creation/deletion at subscription level?” → Activity Log.
-
“Which log stores network security group flow records?” → Diagnostic Logs.
What to Expect in the Exam
-
Direct Q: “Which Azure service is the foundation for monitoring telemetry?” → Azure Monitor.
-
Scenario Q: “Company needs to know who deleted a VM last week.” → Activity Logs.
-
Scenario Q: “Company wants near real-time monitoring of performance.” → Metrics.
-
Trick Q: “Metrics and Logs in Azure Monitor provide identical data.” → False.