Azure Monitor Metrics and Alerts
You'll learn how Azure Monitor organizes metrics, creates custom alert rules, and triggers automated responses through action groups.
What Are Azure Monitor Metrics?
Azure Monitor collects metrics (numeric time-series data) from your Azure resources automatically. Think of it like a dashboard in your car: CPU percentage is your speedometer, memory usage is your fuel gauge, and disk I/O is your RPM meter—all continuously updating.
Metric Namespaces
Azure organizes metrics into namespaces to avoid naming collisions. The format follows ResourceProvider/ResourceType, like:
Microsoft.Compute/virtualMachinesfor VM metricsMicrosoft.Storage/storageAccountsfor storage metrics- Custom namespaces for your application metrics:
CustomApp/Orders
Within each namespace, individual metrics exist (e.g., Percentage CPU, Available Memory Bytes). This structure mirrors what you learned with CloudWatch namespaces, but Azure's naming is more hierarchical.
Creating Alert Rules
Alert rules in Azure Monitor evaluate metrics against conditions you define:
- Scope: Which resource(s) to monitor
- Condition: Threshold and comparison operator (greater than, less than)
- Evaluation frequency: How often to check (1, 5, 15 minutes)
- Aggregation: Sum, average, min, max, count over time
When a condition triggers, the alert enters a "Fired" state (similar to CloudWatch's ALARM state).
Action Groups
Action groups define what happens when an alert fires—the notifications and automated responses. One action group can contain multiple actions:
- Send email/SMS notifications
- Trigger webhooks to external systems
- Execute Azure Functions or Logic Apps
- Create ITSM tickets automatically
You can reuse the same action group across multiple alert rules, making management efficient.
Key Takeaway: Azure Monitor metrics use namespaces for organization, alert rules define monitoring conditions, and action groups execute automated responses—creating a complete monitoring pipeline from detection to action.