Health score. A health score provides real-time insight into the overall health and performance of your monitored entities. The health score is calculated based on anomalies detected for the entity, alerts triggered for the entity's metrics, and the status of the entity. The health score is displayed as a single numerical value that ranges from a Good (70-100) to Moderate (40-69) to Bad (0-39) distinction.

To view the health score for Azure VM and other host type entities in the Metrics Explorer, filter the sw.metrics.healthscore metric by entity_types and select host.

Total number of credits consumed by the Virtual Machine

Total number of credits available to burst

The percentage of allocated compute units that are currently in use by the Virtual Machine(s)

The number of successful read operations from the data disk cache. A higher value indicates efficient caching performance.

The number of read operations that were not found in the data disk cache, requiring retrieval from the underlying storage.

The number of successful read operations from the OS disk cache, improving performance by reducing direct disk access.

The number of read operations that were not found in the OS disk cache, leading to additional disk access.

The percentage of allocated bandwidth consumed by data disk operations. A high percentage may suggest bandwidth saturation.

The percentage of allocated IOPS (Input/Output Operations Per Second) consumed by data disk operations. A high percentage may indicate performance bottlenecks.

The maximum bandwidth that a data disk can achieve when bursting is enabled. This allows temporary performance boosts beyond the provisioned limits.

The maximum IOPS (Input/Output Operations Per Second) a data disk can reach during burst periods. This helps handle short-term spikes in workload demand.

The number of outstanding I/O requests waiting to be processed by the data disk. A higher queue depth may indicate disk contention or performance bottlenecks.

The total number of bytes read from the data disk over a given period. This metric helps monitor disk read performance and workload patterns.

The total number of read operations performed on the data disk. This metric is useful for analyzing disk activity and optimizing performance.

The expected bandwidth allocation for a data disk based on its provisioned performance tier. This helps ensure consistent throughput for workloads.

Represents the expected IOPS (Input/Output Operations Per Second) allocation for a data disk based on its provisioned performance tier. This helps ensure consistent disk performance.

The total number of bytes written to the data disk over a given period. This metric helps monitor disk write performance and workload patterns.

The total number of write operations performed on the data disk. This metric is useful for analyzing disk activity and optimizing performance.

The percentage of allocated bandwidth consumed by the OS disk. A high percentage may indicate bandwidth saturation.

The percentage of allocated IOPS (Input/Output Operations Per Second) consumed by the OS disk. A high percentage may suggest performance bottlenecks.

The maximum bandwidth that the OS disk can achieve when bursting is enabled. This allows temporary performance boosts beyond the provisioned limits.

The maximum IOPS the OS disk can reach during burst periods. This helps handle short-term spikes in workload demand.

The number of outstanding I/O requests waiting to be processed by the OS disk. A higher queue depth may indicate disk contention or performance bottlenecks.

The total number of bytes read from the OS disk over a given period. This metric helps monitor disk read performance and workload patterns.

The total number of read operations performed on the OS disk. This metric helps monitor disk activity and performance.

The expected bandwidth allocation for the OS disk based on its provisioned performance tier. This helps ensure consistent throughput for workloads.

The expected IOPS (Input/Output Operations Per Second) allocation for the OS disk based on its provisioned performance tier. This helps maintain stable disk performance.

The total number of bytes written to the OS disk over a given period. This metric helps monitor disk write performance and workload patterns.

The total number of write operations performed on the OS disk. This metric helps monitor disk activity and performance.

Bytes read from disk during monitoring period

Disk Read IOPS.

Bytes written to disk during monitoring period.

Disk Write IOPS.

The amount of physical memory, in bytes, immediately available for allocation to a process or for system use in the virtual machine.

The number of billable bytes received on all network interfaces by the Virtual Machine(s) (Incoming Traffic).

The number of inbound network flows to the virtual machine. This metric helps monitor network traffic and connection patterns.

The maximum rate at which inbound network flows are created for the virtual machine. This metric helps assess network performance and connection handling.

The total amount of outbound network traffic from the virtual machine. This metric helps monitor bandwidth usage and network performance.

The number of outbound network flows from the virtual machine. This metric helps monitor outgoing connections and network activity.

The maximum rate at which outbound network flows are created for the virtual machine. This metric helps assess network performance and connection handling.

The total amount of inbound network traffic received by the virtual machine. This metric helps monitor bandwidth usage and network performance.

the total amount of outbound network traffic sent from the virtual machine. This metric helps monitor outgoing bandwidth usage and network efficiency.