Azure
The Azure module watches Azure resources through the platform's own APIs: virtual machine power and CPU, Azure SQL Database load and storage, PostgreSQL flexible servers, VPN tunnels and application gateways, and Recovery Services backup jobs. Its values come from the Azure Monitor source, read with read-only roles.
What it monitors
| Area | Checks | Why it matters |
|---|---|---|
| Virtual machines | Power state, CPU as the host sees it | A deallocated VM is an outage the guest cannot report |
| Azure SQL Database | DTU or vCore use, storage used, deadlocks | A database at its DTU or storage limit throttles or stops writes |
| PostgreSQL flexible servers | CPU, memory and storage | The same limits for PostgreSQL in Azure |
| Network | VPN gateway tunnel state; Application Gateway backend health and 5xx responses | A dropped tunnel or an unhealthy backend cuts users off from healthy servers |
| Backup | Failed Recovery Services vault backup jobs | A backup that fails silently is a restore you cannot do |
| Service Health | Azure Service Health events | Tells you when the problem is Azure's, not yours |
Thresholds follow the Azure Monitor recommended alert rules. Every check, with its rule, cause and action, is in the reference for Azure checks. Pending updates of Azure VMs, from Azure Update Manager, are in the Updates module; posture of storage, key vaults and network security groups is in Cloud security.
Before you begin
-
The Azure Monitor source, with the server's managed identity or a service principal. See Connect Azure Monitor.
-
Read-only roles on each subscription, or on a management group:
Role Role ID For Reader acdd72a7-3385-48ef-bd42-f606fba81ae7Inventory, Resource Graph checks such as power state and backup jobs, fired alerts Monitoring Reader 43d0d8ad-25c7-4714-9337-8ba259a9fe05Platform metrics -
The module is on. The feature
monitoring.azurecovers this module and Azure Data Factory; the featuresources.azure_monitorcovers the source.
Azure Service Health events are read by the native collector with the server's identity, on a Monitoring platform itself resource; the source does not compute them.
Add a resource
You do not add Azure resources by hand. The Azure Monitor source lists them with one Resource Graph query over its subscriptions, limited to the resource types you choose, and adds them under the source's entity. Their checks appear the first time the source reports them.
A VM that New Relic or NinjaOne also reports is one resource: sources match it by its resource ID, its fully qualified name or its host name.