Azure Virtual Machine Monitoring

Starter

Professional

Bleemeo collects metrics for Azure Virtual Machines via Azure Monitor (Microsoft.Compute/virtualMachines namespace). Metrics are polled every 1 minute.

Note

If you have the Bleemeo agent running on your VM, it already sends these metrics with higher resolution (10 seconds). In that case, enabling the Azure VM integration will result in duplicate metrics. We recommend using the Bleemeo agent for this VM instead.

Metrics

Metric	Description
cpu_used	CPU usage as a percentage
mem_used_perc	Memory used as a percentage
vm_cpu_credit_usage	Number of CPU credits consumed (burstable B-series VMs only)
vm_cpu_credit_balance	Available CPU credit balance (burstable B-series VMs only)
io_read_bytes	Disk read throughput in bytes per second — the OS disk, or one attached data disk per item
io_write_bytes	Disk write throughput in bytes per second — the OS disk, or one attached data disk per item
io_reads	Disk read operations per second — the OS disk, or one attached data disk per item
io_writes	Disk write operations per second — the OS disk, or one attached data disk per item
net_bits_recv	Network traffic received in bits per second
net_bits_sent	Network traffic sent in bits per second

Note

The vm_cpu_credit_usage and vm_cpu_credit_balance metrics only report data on burstable B-series VMs. All metrics on this page are host-level platform metrics, collected automatically by Azure without any extension or agent configuration.

Note

io_read_bytes, io_write_bytes, io_reads and io_writes report the OS disk by default (item disk_os). Each attached data disk is reported separately, with its item named after its LUN (logical unit number). Azure numbers LUNs from zero, so the first data disk is disk0, the second disk1, and so on.

Note

Stopped or deallocated VMs are not polled: Azure reports no host metrics for them, so expect a gap on every metric on this page for as long as the VM is off. Bleemeo marks such a VM as disconnected, and collection resumes on its own when the VM restarts.

Permissions

Requires the Monitoring Reader role and the Microsoft.Insights resource provider registered on the subscription — see Permissions Summary.

Estimated Azure Cost

$0.432/month per batch of up to 50 running VMs in the same region (1 Azure Monitor API call per minute) — see Estimated Azure Costs. Stopped VMs are not polled and cost nothing.

VMs with at least one attached data disk make a second, separate API call per minute (to retrieve per-disk metrics), roughly doubling the cost for that batch to ~$0.864/month — regardless of how many data disks are attached (1 or 15 costs the same, since it’s still a single additional call).

See Also

• Configuration — set up Azure credentials and permissions
• Agent Installation — install the Bleemeo agent for higher-resolution metrics