In today’s Ask the Admin, I’ll show you how to set up metrics in Azure Monitor.
In Azure Monitor: Logs and Saving Queries on the Petri IT Knowledgebase, I showed you how to view and filter the results of the activity logs, save your queries, and view and enable diagnostic logging. But Azure Monitor has a couple of other features, called metrics and alerts, that allow us to configure performance thresholds and trigger alerts if they are exceeded.
Metrics collect information about resources you create in Azure, and about the Azure fabric. They can be used for tracking performance issues, used as the source information for alert notifications; and to initiate automated actions, such as autoscaling resources or starting an Azure runbook.
In the instructions below, I’ll show you how to set up a metric for virtual machine (VM) CPU usage. For VMs, Azure divides some metrics into two categories: guest-os-level and host-os-level. Host-os-level metrics show information about the Hyper-V host server, and guest-os-level metrics about the VMs you create in Azure. Before guest-os-level metrics can be collected for a VM, diagnostic logging must be enabled, which you can do by either completing the instructions in Azure Monitor: Logs and Saving Queries, or by modifying the diagnostic logging option in the VM’s settings panel.
The first task is to determine the resource type for which we want to create a metric:
A list of available metrics for the resource will now appear below the drop-down menus.
In the Plot section of the Monitor – Metrics panel, you’ll see a graphical representation of your chosen metrics, which you can customize by changing the type of graph and polling frequency using the drop-down menus above the graph. It’s also possible to pin the metric to the portal dashboard by clicking Pin to the dashboard in the top right of the panel.
In this article, I showed you how to set up metrics in Azure Monitor. In a forthcoming article, I’ll show you how to set up alerts.