3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
2 VMware, Inc.
Contents
About vRealize Operations Manager Reference for Metrics, Properties, and Alerts5
Metric Denitions in vRealize Operations Manager7
1
Metrics for vCenter Server Components 8
Calculated Metrics 76
Self-Monitoring Metrics for vRealize Operations Manager 82
Metrics for vRealize Automation 107
Metrics for vSAN 107
Metrics for the Operating Systems and Remote Service Monitoring Plug-ins in
End Point Operations Management 114
Property Denitions in vRealize Operations Manager131
2
Properties for vCenter Server Components 131
Self-Monitoring Properties for vRealize Operations Manager 144
Properties for vSAN 146
Alert Denitions in vRealize Operations Manager149
3
Cluster Compute Resource Alert Denitions 150
Host System Alert Denitions 154
vRealize Automation Alert Denitions 168
vSAN Alerts Denitions 169
Alerts in the vSphere Web Client 176
vSphere Distributed Port Group 176
Virtual Machine Alert Denitions 177
vSphere Distributed Switch Alert Denitions 185
vCenter Server Alert Denitions 186
Datastore Alert Denitions 187
Data Center Alert Denitions 192
Custom Data Center Alert Denitions 193
Index195
VMware, Inc. 3
vRealize Operations Definitions for Metrics, Properties, and Alerts
4 VMware, Inc.
About vRealize Operations Manager Reference
for Metrics, Properties, and Alerts
The vRealize Operations Manager Reference for Metrics, Properties, and Alerts provides information about the
metric, properties, and alert denitions provided with vRealize Operations Manager.
Intended Audience
This information is intended for anyone who wants to install and congure vRealize Operations Manager by
using a virtual appliance deployment. The information is wrien for experienced virtual machine
administrators who are familiar with enterprise management applications and datacenter operations.
VMware Technical Publications Glossary
VMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For denitions
of terms as they are used in VMware technical documentation, go to
hp://www.vmware.com/support/pubs.
VMware, Inc.
5
vRealize Operations Definitions for Metrics, Properties, and Alerts
6 VMware, Inc.
Metric Definitions in
vRealize Operations Manager1
Metric denitions provide an overview of how the metric value is calculated or derived. If you understand
the metric, you can beer tune vRealize Operations Manager to display results that help you to manage
your environment.
vRealize Operations Manager collects data from objects in your environment. Each piece of data collected is
called a metric observation or value. vRealize Operations Manager uses the VMware vCenter® adapter to
collect raw metrics. vRealize Operations Manager uses the vRealize Operations Manager adapter to collect
self-monitoring metrics. In addition to the metrics it collects, vRealize Operations Manager calculates
capacity metrics, badge metrics, and metrics to monitor the health of your system.
All metric denitions are provided. The metrics reported on your system depend on the objects in your
environment. You can use metrics to help troubleshoot problems. See the vRealize Operations Manager UserGuide.
Changes in Metric Availability
The CPU Demand of Recommended (%) metric is no longer available in vRealize Operations Manager
version 6.x. To approximate the metric, create a super metric using the following calculations, and add it to
your Views and Reports as needed.
For more information about super metrics, see the vRealize Operations Manager Information Center.
This chapter includes the following topics:
“Metrics for vCenter Server Components,” on page 8
n
“Calculated Metrics,” on page 76
n
“Self-Monitoring Metrics for vRealize Operations Manager,” on page 82
n
“Metrics for vRealize Automation,” on page 107
n
“Metrics for vSAN,” on page 107
n
“Metrics for the Operating Systems and Remote Service Monitoring Plug-ins in End Point Operations
n
Management,” on page 114
VMware, Inc.
7
vRealize Operations Definitions for Metrics, Properties, and Alerts
Metrics for vCenter Server Components
vRealize Operations Manager connects to VMware vCenter Server® instances through the vCenter adapter
to collect metrics for vCenter Server components and uses formulas to derive statistics from those metrics.
You can use metrics to troubleshoot problems in your environment.
vCenter Server components are listed in the describe.xmlle for the vCenter adapter. The following
example shows sensor metrics for the host system in the describe.xmlle.
Each ResourceAttribute element includes the name of a metric that appears in the UI and is documented as
a Metric Key.
Table 1‑1. Sensor Metrics for Host System Cooling
Metric KeyMetric NameDescription
Sensor|fan|currentValueSpeedFan speed.
Sensor|fan|healthStateHealth StateFan health state.
Sensor|temperature|currentValueTemperatureHost system temperature.
Sensor|temperature|healthStateHealth StateHost system health state.
vSphere Metrics
vRealize Operations Manager collects CPU use, disk, memory, network, and summary metrics for objects in
the vSphere world.
Capacity metrics can be calculated for vSphere world objects. See “Capacity and Project-Based Metrics,” on
page 77.
CPU Usage Metrics
CPU usage metrics provide information about CPU use.
8 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
Table 1‑2. CPU Usage Metrics
Metric NameDescription
CPU|Capacity usageCPU usages as a percent during the interval.
Key: cpu|capacity_usagepct_average
CPU|CPU contention(%)This metric shows the percentage of time the VMs in the ESXi hosts are
unable to run because they are contending for access to the physical CPUs.
The number shown is the average number for all VMs. The number will be
lower than the highest number experienced by the VM that is most impacted
by CPU contention.
Use this metric to verify if the host can serve all its VMs eciently. Low
contention means that the VM can access everything it demands to run
smoothly. It means that the infrastructure is providing good service to the
application team.
When using this metric, ensure that the number is within your expectation.
Look at both the relative number and the absolute number. Relative means a
drastic change in value, meaning that the ESXi is unable to serve the VMs.
Absolute means that the real value itself is high. Investigate why the number
is high. One factor that impacts this metric is CPU Power Management. If
CPU Power Management clocks down the CPU speed from 3 GHz to 2 GHz,
the reduction in speed is accounted for because it shows that the VM is not
running at full speed.
This metric is calculated in the following way: cpu|capacity_contention / (200
* summary|number_running_vcpus)
Key: cpu|capacity_contentionPct
CPU|Demand (%)This metric shows the amount of CPU resources a virtual machine would use
if there were no CPU contention or CPU limit. This metric represents the
average active CPU load for the past ve minutes.
Keep this number below 100% if you set the power management to
maximum.
This metric is calculated in the following way: ( cpu.demandmhz /
cpu.capacity_provisioned)*100
Key: cpu|demandPct
CPU|Demand (MHz)This metric shows the amount of CPU resources a virtual machine would use
if there were no CPU contention or CPU limit.
Key: cpu|demandmhz
CPU|DemandCPU demand in megaher.
Key: cpu|demand_average
CPU|IO waitIO wait (ms).
Key: cpu|iowait
CPU|number of CPU SocketsNumber of CPU sockets.
Key: cpu|numpackages
CPU|Overall CPU ContentionOverall CPU contention in milliseconds.
Key: cpu|capacity_contention
CPU|Provisioned Capacity (MHz)capacity in MHz of the physical CPU cores.
Key: cpu|capacity_provisioned
CPU|Provisioned vCPU(s)Number of provisioned CPU cores.
Key: cpu|corecount_provisioned
CPU|Reserved Capacity (MHz)Total CPU capacity reserved by virtual machines.
Key: cpu|reservedCapacity_average
VMware, Inc. 9
vRealize Operations Definitions for Metrics, Properties, and Alerts
Table 1‑2. CPU Usage Metrics (Continued)
Metric NameDescription
CPU|Usage (MHz)CPU usages, as measured in megaher, during the interval.
n
n
Key: cpu|usagemhz_average
CPU|WaitTotal CPU time spent in wait state. The wait total includes time spent in the
CPU Idle, CPU Swap Wait, and CPU I/O Wait states.
Key:cpu|wait
CPU|Workload (%)Percent of workload
Key: cpu|workload
Memory Metrics
Memory metrics provide information about memory use and allocation.
VM - Amount of actively used virtual CPU. This is the host's view of the
CPU usage, not the guest operating system view.
Host - Sum of the actively used CPU of all powered on virtual machines
on a host. The maximum possible value is the frequency of the two
processors multiplied by the number of processors. For example, if you
have a host with four 2 GHz CPUs running a virtual machine that is
using 4000 MHz, the host is using two CPUs completely: 400 / (4 2000) =
0.50
Table 1‑3. Memory Metrics
Metric NameDescription
mem|Contention (%)This metric shows the percentage of time VMs are waiting to access swapped
memory.
Use this metric to monitor ESXi memory swapping. A high value indicates
that the ESXi is running low on memory, and a large amount of memory is
being swapped.
Key: mem|host_contentionPct
mem|Machine Demand (KB)Host memory demand in kilobytes.
Key: mem|host_demand
mem|Provisioned MemoryProvisioned host memory in kilobytes.
Key: mem|host_provisioned
mem|Reserved Capacity (KB)Total amount of memory reservation used by powered-on virtual machines
and vSphere services on the host.
Key: mem|reservedCapacity_average
mem|Usable Memory (KB)Usable host memory in kilobytes.
Key: mem|host_usable
mem|Host Usage (KB)Host memory use in kilobytes.
Key: mem|host_usage
mem|Usage/Usable (%)Memory usage as percentage of total congured or available memory.
Key: mem|host_usagePct
mem|Workload (%)Percent of workload.
Key: mem|workload
Network Metrics
Network metrics provide information about network performance.
10 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
Table 1‑4. Network Metrics
Metric NameDescription
net|Packets Dropped (%)This metric shoes the percentage of received and transmied packets
dropped in the collection interval.
Use this metric to monitor the reliability and performance of the ESXi
network. A high value indicates that the network is not reliable and
performance decreases.
Key: net|droppedPct
net|Usage Rate (KB per second)Sum of the data transmied and received for all of the NIC instances of the
host or virtual machine.
Key: net|usage_average
net|Workload (%)Percent of workload.
Key: net|workload
Disk Metrics
Disk metrics provide information about disk use.
Table 1‑5. Disk Metrics
Metric NameDescription
disk|Commands per secondAverage number of commands issued per second during the collection
cycle.
Key: disk|commandsAveraged_average
disk|Usage Rate (KB per second)Average of the sum of the data read and wrien for all of the disk instances
of the host or virtual machine.
Key: disk|usage_average
disk|Workload (%)Percent of workload.
Key: disk|workload
Summary Metrics
Summary metrics provide information about overall performance.
Table 1‑6. Summary Metrics
Metric NameDescription
summary|Number of Running HostsNumber of running hosts.
Key: summary|number_running_hosts
summary|Number of Running VMsThis metric shows the number of running VMs at a given point in time.
The data is sampled every ve minutes.
A large number of running VMs might be a reason for CPU or memory
spikes because more resources are used in the host. The number of
running VMs gives you a good indicator of how many requests the ESXi
host must juggle. Powered o VMs are not included because they do not
impact ESXi performance. A change in the number of running VMs can
contribute to performance problems. A high number of running VMs in
a host also means a higher concentration risk, because all the VMs will
fail if the ESXi crashes.
Use this metric to look for a correlation between spikes in the running
VMs and spikes in other metrics such as CPU contention, or memory
contention.
Key: summary|number_running_vms
summary|Total Number of ClustersTotal number of clusters.
Key: summary|total_number_clusters
VMware, Inc. 11
vRealize Operations Definitions for Metrics, Properties, and Alerts
Table 1‑6. Summary Metrics (Continued)
Metric NameDescription
summary|Total Number of DatastoresTotal number of datastores.
summary|Total Number of HostsTotal number of hosts.
summary|Total Number of VMsTotal number of virtual machines.
summary|Total Number of DatacentersTotal number of data centers.
summary|Number VCPUs on Powered on
VMs
summary|Average Running VM Count per
Running Host
vCenter Server Metrics
vRealize Operations Manager collects CPU use, disk, memory, network, and summary metrics for vCenter
Server system objects.
Key: summary|total_number_datastores
Key: summary|total_number_hosts
Key: summary|total_number_vms
Key: summary|total_number_datacenters
Number of virtual CPUs on powered-on virtual machines.
Key: summary|number_running_vcpus
Average running virtual machine count per running host.
Key: summary|avg_vm_density
vCenter Server metrics include capacity and badge metrics. See denitions in:
“Capacity and Project-Based Metrics,” on page 77
n
“Badge Metrics,” on page 80
n
CPU Usage Metrics
CPU usage metrics provide information about CPU use.
Datastore metrics provide information about the datastore.
Table 1‑8. Datastore Metrics
Metric KeyMetric NameDescription
datastore|
maxObserved_NumberRead
datastore|maxObserved_ReadMax Observed Read RateMax observed rate of reading data from the
datastore|
maxObserved_NumberWrite
datastore|maxObserved_WriteMax Observed Write RateMax observed rate of writing data from the
datastore|maxObserved_OIOMax Observed Number of
datastore|demand_oioOutstanding IO requestsOIO for datastore.
datastore|
numberReadAveraged_average
datastore|
numberWriteAveraged_average
datastore|read_averageRead RateAmount of data read in the performance interval.
datastore|write_averageWrite RateAmount of data wrien to disk in the performance
Max Observed Reads per
second
Max Observed Writes per
second
Outstanding IO Operations
Reads per secondAverage number of read commands issued per
Writes per secondAverage number of write commands issued per
Max observed average number of read commands
issued per second during the collection interval.
datastore.
Max observed average number of write commands
issued per second during the collection interval.
datastore.
Maximum observed number of outstanding IO
operations.
second during the collection interval.
second during the collection interval.
interval.
Disk Metrics
Disk metrics provide information about disk use.
Table 1‑9. Disk Metrics
Metric KeyMetric NameDescription
disk|commandsAveraged_averageCommands per secondAverage number of commands issued per second
during the collection cycle.
disk|totalLatency_averageDisk Command Latency
(ms)
disk|usage_averageUsage Rate (KBps)Average of the sum of the data read and wrien for
disk|sum_queued_oioTotal queued outstanding
operations
disk|max_observedMax Observed OIOMax observed IO for a disk.
VMware, Inc. 13
Average amount of time taken for a command from
the perspective of the guest operating system. This
metric is the sum of the Kernel Device Command
Latency and Physical Device Command Latency
metrics.
all of the disk instances of the host or virtual
machine.
Sum of queued operations and outstanding
operations.
vRealize Operations Definitions for Metrics, Properties, and Alerts
Diskspace Metrics
Disk space metrics provide information about disk space use.
Table 1‑10. Diskspace Metrics
Metric KeyMetric NameDescription
diskspace|total_usageTotal disk space used (KB)Total disk space used on all datastores visible to
diskspace|total_capacityTotal disk space (KB)Total disk space on all datastores visible to this
diskspace|total_provisionedTotal provisioned disk space
(KB)
Memory Metrics
Memory metrics provide information about memory use and allocation.
* CPU|CPU Contention (%)CPU contention as a percentage of 20-second collection
interval.
Key: cpu|capacity_contentionPct
CPU|Capacity ProvisionedProvisioned CPU capacity in megahertrz.
Key: cpu|capacity_provisioned
CPU|Demand (MHz)CPU demand in megaher.
Key: cpu|demandmhz
CPU|Host demand for aggregationHost demand for aggregation.
Key: cpu|host_demand_for_aggregation
CPU|Demand (ms)The total CPU time that the VM could use if there was
no contention.
Key: cpu|demand_average
CPU|Demand (%)CPU demand as a percentage of the provisioned
capacity.
Key: cpu|demandPct
CPU|Dynamic EntitlementCPU Dynamic Entitlement.
Key: cpu|dynamic_entitlement
* CPU|Usage (%)This metric indicates the percentage of CPU that was
used out of all the CPU that was allocated to the VM.
CPU usage can indicate if the VM is undersized.
Key: cpu|usage_average
CPU|Usage (MHz)CPU use in megaher.
Key: cpu|usagemhz_average
CPU|System (ms)CPU time spent on system processes.
Key: cpu|system_summation
VMware, Inc. 17
vRealize Operations Definitions for Metrics, Properties, and Alerts
MetricDescription
CPU|Wait (ms)Total time that a virtual CPU can not be run. It could
CPU|Ready (ms)CPU time spent in the ready state.
* CPU|Ready (%)This metric indicates the percentage of time in which
CPU|Used (ms)CPU time that is used.
CPU|Extra (ms)Extra CPU time in milliseconds.
CPU|Guaranteed (ms)CPU time that is guaranteed for the virtual machine.
CPU|Swap Wait (ms)Swap wait time in milliseconds.
CPU|Co-stop (ms)Time the VM is ready to run, but is unable to due to
CPU|Co-stop (%)Percentage of time the VM is ready to run, but is
CPU|Idle (ms)CPU time that is idle.
CPU|LatencyPercentage of time the VM is unable to run because it
CPU|Max LimitedTime the VM is ready to run, but is not run due to
CPU|OverlapTime the VM was interrupted to perform system
CPU|RunTime the VM is scheduled to run.
CPU|Entitlement LatestEntitlement Latest.
be idle (halted) or waiting for an external event such as
I/O.
Key: cpu|wait_summation
Key: cpu|ready_summation
the VM was waiting in line to use the CPU on the host.
A large ready time for a VM indicates that the VM
needed CPU resources but the infrastructure was busy
serving other VMs. This might indicate that the host is
trying to serve too many VMs.
Whenever the CPU ready is larger than 10%, you
should check if the host is overloaded, or if the VM
really needs all the resources that were allocated to it.
Key: cpu|readyPct
Key: cpu|used_summation
Key: cpu|extra_summation
Key: cpu|guaranteed_latest
Key: cpu|swapwait_summation
co-scheduling constraints.
Key: cpu|costop_summation
unable to due to co-scheduling constraints.
Key: cpu|costopPct
Key: cpu|idle_summation
is contending for access to the physical CPUs.
Key: cpu|latency_average
maxing out its CPU limit seing.
Key: cpu|maxlimited_summation
services on behalf of that VM or other VMs.
Key: cpu|overlap_summation
Key: cpu|run_summation
Key: cpu|entitlement_latest
CPU Utilization for Resources Metrics for Virtual Machines
CPU utilization for resources metrics provide information about resource CPU use.
18 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
MetricDescription
rescpu|CPU Active (%) (interval)The average active time (actav) or peak active time (actpk) for the CPU
during various intervals.
Key:
rescpu|actav1_latest
rescpu|actav5_latest
rescpu|actav15_latest
rescpu|actpk1_latest
rescpu|actpk5_latest
rescpu|actpk15_latest
rescpu|CPU Running (%) (interval)The average runtime (runav) or peak active time (runpk) for the CPU
during various intervals.
Key:
rescpu|runav1_latest
rescpu|runav5_latest
rescpu|runav15_latest
rescpu|runpk1_latest
rescpu|runpk5_latest
rescpu|runpk15_latest
rescpu|CPU Throled (%) (interval)Amount of CPU resources over the limit that were refused, average
over various intervals.
Key:
rescpu|maxLimited1_latest
rescpu|maxLimited5_latest
rescpu|maxLimited15_latest
rescpu|Group CPU Sample CountThe sample CPU count.
Key: rescpu|sampleCount_latest
rscpu|Group CPU Sample Period (ms)The sample period.
Key: rscpu|samplePeriod_latest
Memory Metrics for Virtual Machines
Memory metrics provide information about memory use and allocation.
MetricDescription
Mem|Host Active (KB)Host active memory use in kilobytes.
Key: mem|host_active
Mem|Usage (KB)Memory use in kilobytes.
Key: mem|host_usage
Mem|Contention (KB)Memory contention in kilobytes.
Key: mem|host_contention
Mem|Contention (%)Percent memory contention.
Key: mem|host_contentionPct
Mem|Guest Congured Memory (KB)Guest operating system congured memory in kilobytes.
Disk|Disk Read LatencyThe average amount of time taken for a read from the
during the collection interval.
Key: disk|commandsAveraged_average
Key: disk|usage_average
disk|workload. storage|usage_average is an average
over all storage devices. This means that disk|
usage_capacity is not specic to the selected VM or the
host of the VM.
Key: disk|usage_capacity
Key: disk|diskoio
Key: disk|diskqueued
Key: disk|diskdemand
Operations.
Key: disk |sum_queued_oio
Key: disk|max_observed
Key: disk|read_average
interval.
Key: disk|write_average
dened interval.
Key: disk|numberRead_summation
dened interval.
Key: disk|numberWrite_summation
Key: disk|busResets_summation
performance interval.
Key: disk|commands_summation
performance interval.
Key: disk|commandsAborted_summation
Key: disk|maxTotalLatency_latest
Key: disk|scsiReservationConicts_summation
perspective of a Guest OS. This is the sum of Kernel
Read Latency and Physical Device Read Latency.
Key: disk|totalReadLatency_average
24 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
MetricDescription
Disk|Disk Write LatencyThe average amount of time taken for a write from the
perspective of a Guest OS. This is the sum of Kernel
Write Latency and Physical Device Write Latency.
Key: disk|totalWriteLatency_average
Disk|Disk Command Latency (ms)The average amount of time taken for a command from
the perspective of a Guest OS. This is the sum of Kernel
Command Latency and Physical Device Command
Latency.
Key: disk|totalLatency_average
Virtual Disk Metrics for Virtual Machines
Virtual disk metrics provide information about virtual disk use.
MetricDescription
VirtualDisk|UsageAverage CPU usage as a percentage.
Key: virtualDisk|usage
VirtualDisk|Total LatencyTotal latency.
Key: virtualDisk|totalLatency
VirtualDisk|Commands Per SecondAverage number of commands per second.
Key: virtualDisk|commandsAveraged_average
VirtualDisk|Read RequestsAverage number of read commands issued per second
to the virtual disk during the collection interval.
Key: virtualDisk|numberReadAveraged_average
VirtualDisk|Write RequestsAverage number of write commands issued per second
to the virtual disk during the collection interval.
Key: virtualDisk|numberWriteAveraged_average
VirtualDisk|Read Rate (KBps)Rate of reading data from the virtual disk in kilobytes
per second.
Key: virtualDisk|read_average
VirtualDisk|Read Latency (ms)Average amount of time for a read operation from the
virtual disk. Total latency = kernel latency + device
latency.
Key: virtualDisk|totalReadLatency_average
VirtualDisk|Write Latency (ms)Average amount of time for a write operation to the
virtual disk. Total latency = kernel latency + device
latency.
Key: virtualDisk|totalWriteLatency_average
VirtualDisk|Write Rate (KBps)Rate of writing data from the virtual disk in kilobytes
per second.
Key: virtualDisk|write_average
VirtualDisk|Bus ResetsThe number of bus resets in the performance interval.
Key: virtualDisk|busResets_summation
VirtualDisk|Commands AbortedThe number of disk commands aborted in the
performance interval.
Key: virtualDisk|commandsAborted_summation
VirtualDisk|Read LoadStorage DRS virtual disk metric read load.
Key: virtualDisk|readLoadMetric_latest
VirtualDisk|Outstanding Read RequestsAverage number of outstanding read requests to the
virtual disk.
Key: virtualDisk|readOIO_latest
VMware, Inc. 25
vRealize Operations Definitions for Metrics, Properties, and Alerts
MetricDescription
VirtualDisk|Write LoadStorage DRS virtual disk write load.
VirtualDisk|Outstanding Write RequestsAverage number of outstanding write requests to the
VirtualDisk|Number of Small SeeksSmall Seeks.
VirtualDisk|Number of Medium SeeksMedium Seeks.
VirtualDisk|Number of Large SeeksLarge Seeks.
VirtualDisk|Read Latency (microseconds)Read Latency in microseconds.
VirtualDisk|Write Latency (microseconds)Write Latency in microseconds.
Guest le system metrics provide information about guest le system capacity and free space.
MetricDescription
Guest le system|Guest File System Capacity (MB)Total capacity on guest le system in megabytes.
Key: guestlesystem|capacity
Guest le system|Guest File System Free (MB)Total free space on guest le system in megabytes.
Key: guestlesystem|freespace
Guest le system|Guest File System Usage (%)Percent guest le system.
Key: guestlesystem|percentage
Guest le system|Guest File System UsageTotal usage of guest le system.
Key: guestlesystem|usage
* Guest le system|Total Guest File System Free (GB)This metric displays the amount of free disk space from all le
systems aached to this VM.
Use this metric to see if there are spikes in the free space or if
there is an organic growth for this VM.
Key: guestlesystem|freespace_total
* Guest le system|Total Guest File System Capacity
(GB)
This metric displays the amount of disk space allocated for the
VM.
Correlate other metrics with this metric to indicate if changes
occur in the disk space allocation for the VM.
Key: guestlesystem|capacity_total
26 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
MetricDescription
* Guest le system|Total Guest File System Usage (%)This metric displays the amount of displa space being used out
of the total allocated disk space.
Use his metric to track if the overall usage is stable, or if it
reaches the limits. You should avoid having VMs with a disk
space usage of >95% since this could impact your system.
Key: guestlesystem|percentage_total
Guest le system|Total Guest File System UsageTotal usage of guest le system.
Key: guestlesystem|usage_total
Network Metrics for Virtual Machines
Network metrics provide information about network performance.
MetricDescription
Net|Demand (%)Percent demand.
Key: net|demand
Net|Usage Rate (KBps)The sum of the data transmied and received for all the NIC
instances of the host or virtual machine.
Key: net|usage_average
Net|Packets Received per secondNumber of packets received in the performance interval.
Key: net|packetsRxPerSec
Net|Packets Transmied per secondNumber of packets transmied in the performance interval.
Key: net|packetsTxPerSec
* Net|Data Transmit Rate (KBps)This metric shows the rate of data being sent by the VM per
second.
Key: net|transmied_average
* Net|Data Receive Rate (KBps)This metric shows the rate of data received by the VM per
second.
Key: net|received_average
Net|Packets per secondNumber of packets transmied and received per second.
Key: net|PacketsPerSec
Net|I/O Usage CapacityIO use capacity.
Key: net|usage_capacity
Net|Max Observed Throughput (KBps)Maximum observed throughput in kilobytes per second.
Key: net|maxObserved_KBps
Net|Max Observed Transmied ThroughputMax observed transmied rate of network throughput.
Key: net|maxObserved_Tx_KBps
Net|Max Observed Received ThroughputMax observed received rate of network throughput.
Key: net|maxObserved_Rx_KBps
Net|Packets ReceivedNumber of packets received in the performance interval.
Key: net|packetsRx_summation
Net|Packets TransmiedNumber of packets transmied in the performance interval.
Key: net|packetsTx_summation
* Net|Received Packets DroppedThis metric shows the number of received packets dropped in
the collection interval.
Key: net|droppedRx_summation
* Net|Transmied Packets DroppedThis metric shows the number of transmied packets
dropped in the collection interval
Key: net|dropppedTx_summation
VMware, Inc. 27
vRealize Operations Definitions for Metrics, Properties, and Alerts
MetricDescription
Net|Packets Dropped (%)Percentage of packets dropped.
Net|Packets DroppedNumber of packets dropped in the performance interval.
Net|Broadcast Packets TransmiedNumber of broadcast packets transmied during the
Net|Broadcast Packets ReceivedNumber of broadcast packets received during the sampling
Net|Bytes Rx (KBps)Average amount of data received per second.
Net|Bytes Tx (KBps)Average amount of data transmied per second.
Net|Multicast Packets ReceivedNumber of multicast packets received.
Net|Multicast Packets TransmiedNumber of multicast packets transmied.
Net|VM to Host Data Transmit RateAverage amount of data transmied per second between VM
Net|VM to Host Data Receive RateAverage amount of data received per second between VM
Net|VM to Host Usage RateThe sum of the data transmied and received for all the NIC
Net|VM to Host Max Observed Transmied ThroughputMax observed transmied rate of network throughput
Net|VM to Host Max Observed Received ThroughputMax observed received rate of network throughput between
Net|VM to Host Max Observed ThroughputMax observed rate of network throughput between VM and
vRealize Operations Manager collects many metrics for host systems, including CPU use, datastore, disk,
memory, network, storage, and summary metrics for host system objects.
Capacity metrics can be calculated for host system objects. See “Capacity and Project-Based Metrics,” on
page 77.
Metrics marked with an asterisk (*) provide the most relevant data to use when you troubleshoot the hosts
in your environment.
vFlash Module Metrics for Host Systems
vFlash Module metrics provide information about the host system's ash devices.
MetricDescription
vFlashModule|Latest Number of Active VM DisksLatest Number of Active VM Disks.
Key: vashModule|numActiveVMDKs_latest
Configuration Metrics for Host Systems
Conguration metrics provide information about host system conguration.
machines in the ESXi hosts are unable to run because they are
contending for access to the physical CPU(s). This is the
average number of all VMs. Naturally, the number will be
lower than the highest number experienced by the worst hit
VM (a VM that suers the highest CPU contention).
Use this metric to verify if the host is able to serve all of its
VMs well.
When using this metric, ensure the number is within your
expectation. The metric is aected by several factors so you
need to watch both relative numbers and absolute numbers.
Relative means a drastic change in value. This indicates that
the ESXi is unable to service its VMs.
Absolute means that the real value is high. You should
investigate why the value is high. One factor that impacts the
CPU contention metric is CPU Power Management. If CPU
Power Management clocks down the CPU speed from 3 GHz
to 2 GHz that reduction in speed is taken into account. This is
because the VM is not running at full speed.
Key: cpu|capacity_contentionPct
VMs would use if there was no CPU contention or any CPU
limits set.
It represents the average active CPU load for the past ve
minutes.
Keep the number of this metric below 100% if you set Power
Management to Maximum.
Key: cpu|demandPct
Key: cpu|demandmhz
Key: cpu|iowait
Key: cpu|numpackages
Key: cpu|capacity_contention
Key: cpu|capacity_provisioned
Key: cpu|corecount_provisioned
Key: cpu|wait
Key: cpu|demand_average
32 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
MetricDescription
CPU|Used (msec)Time accounted to the virtual machine. If a system service
runs on behalf of this virtual machine, the time spent by that
service (represented by cpu.system) should be charged to this
virtual machine. If not, the time spent (represented by
cpu.overlap) should not be charged against this virtual
machine.
Key: cpu|used_summation
CPU|Usage (MHz)CPU use in megaher.
Key: cpu|usagemhz_average
CPU|Reserved Capacity (MHz)The sum of the reservation properties of the (immediate)
children of the host's root resource pool.
Key: cpu|reservedCapacity_average
CPU|Total Capacity (MHz)Total CPU capacity in megaher.
Key: cpu|totalCapacity_average
CPU|Idle (ms)CPU idle time in milliseconds.
Key: cpu|idle_summation
CPU|Overhead (KB)Amount of CPU overhead.
Key: cpu|overhead_average
CPU|Demand without overheadValue of demand excluding any overhead.
Key: cpu|demand_without_overhead
CPU|Core Utilization (%)Percent core utilization.
Key: cpu|coreUtilization_average
CPU|Utilization(%)Percent CPU utilization.
Key: cpu|utilization_average
CPU|Core Utilization (%)Core Utilization.
Key: cpu|coreUtilization_average
CPU|Utilization (%)Utilization.
Key: cpu|utilization_average
CPU|Co-stop (ms)Time the VM is ready to run, but is unable to due to co-
scheduling constraints.
Key: cpu|costop_summation
CPU|Latency (%)Percentage of time the VM is unable to run because it is
contending for access to the physical CPUs.
Key: cpu|latency_average
CPU|Ready (ms)Time spent in ready state.
Key: cpu|ready_summation
CPU|Run (ms)Time the virtual machine is scheduled to run.
Key: cpu|run_summation
CPU|Swap wait (ms)Amount of time waiting for swap space.
* Datastore|Average Observed Virtual Machine Disk I/O
Workload
Datastore|Maximum Observed VM Disk I/O WorkloadMaximum Observed VM Disk I/O Workload on the
Datastore|VM Disk I/O Workload DisparityPercentage Disk I/O workload disparity among the
second.
Key: datastore|write_average
Key: datastore|datastoreMaxQueueDepth_latest
Key: datastore|maxTotalLatency_latest
Key: datastore|totalLatency_max
Key: datastore|datastoreNormalReadLatency_latest
Key: datastore|datastoreNormalWriteLatency_latest
Key: datastore|datastoreReadBytes_latest
Key: datastore|datastoreReadIops_latest
Key: datastore|datastoreReadLoadMetric_latest
Key: datastore|datastoreReadOIO_latest
Key: datastore|datastoreWriteBytes_latest
Key: datastore|datastoreWriteIops_latest
Key: datastore|datastoreWriteLoadMetric_latest
Key: datastore|datastoreWriteOIO_latest
Average Observed Virtual Machine Disk I/O
Workload on the Host.
Key: datastore|vmPopulationAvgWorkload
Host.
Key: datastore|vmPopulationMaxWorkload
VMs on the Host.
Key: datastore|vmWorkloadDisparityPc
Disk Metrics for Host Systems
Disk metrics provide information about disk use.
36 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
MetricDescription
Disk|Usage Rate (KBps)Average of the sum of the data read and wrien for all
of the disk instances of the host or virtual machine.
disk|usage_average
Disk|I/O Usage CapacityThis metric is a function of storage|usage_average and
disk|workload. storage|usage_average is an average
over all storage devices. This means that disk|
usage_capacity is not specic to the selected VM or the
host of the VM.
Key: disk|usage_capacity
Disk|Commands per secondAverage number of commands issued per second
during the collection interval.
Key: disk|commandsAveraged_average
Disk|Disk Command Latency (ms)The average amount of time taken for a command
from the perspective of a Guest OS. This is the sum of
Kernel Command Latency and Physical Device
Command Latency.
Key: disk|totalLatency_average
Disk|Reads per secondAverage number of read commands issued per second
during the collection interval.
Key: disk|numberReadAveraged_average
Disk|Writes per secondAverage number of write commands issued per
second during the collection interval.
Key: disk|numberWriteAveraged_average
Disk|Read RequestsNumber of times data was read from the disk in the
dened interval.
Key: disk|numberRead_summation
Disk|Write RequestsNumber of times data was wrien to the disk in the
dened interval.
Key: disk|numberWrite_summation
Disk|Read RateAmount of data read in the performance interval.
Key: disk|read_average
Disk|Write RateAmount of data wrien to disk in the performance
interval.
Key: disk|write_average
Disk|Bus ResetsThe number of bus resets in the performance interval.
Key: disk|busResets_summation
Disk|Commands IssuedThe number of disk commands issued in the
performance interval.
Key: disk|commands_summation
Disk|Commands AbortedThe number of disk commands aborted in the
performance interval.
Key: disk|commandsAborted_summation
Disk|Physical Device Read Latency (ms)The average time taken to complete a read from the
physical device.
Key: disk|deviceReadLatency_average
Disk|Kernel Disk Read Latency (ms)The average time spent in ESX Server VMKernel per
read.
Key: disk|kernelReadLatency_average
VMware, Inc. 37
vRealize Operations Definitions for Metrics, Properties, and Alerts
MetricDescription
Disk|Disk Read Latency (ms)The average amount of time taken for a read from the
Disk|Queue Read Latency (ms)The average time spent in the ESX Server VMKernel
Disk|Physical Device Write Latency (ms)The average time taken to complete a write from the
Disk|Kernel Disk Write Latency (ms)The average time spent in ESX Server VMKernel per
Disk|Disk Write Latency (ms)The average amount of time taken for a write from the
Disk|Queue Write Latency (ms)The average time spent in the ESX Server VMKernel
Disk|Physical Device Command Latency (ms)The average time taken to complete a command from
Disk|Kernel Disk Command Latency (ms)The average time spent in ESX Server VMKernel per
Disk|Queue Command Latency (ms)The average time spent in the ESX Server VMKernel
Disk|Number of Outstanding IO OperationsNumber of Outstanding IO Operations.
Disk|Queued OperationsQueued Operations.
Disk|DemandDemand.
Disk|Total Queued Outstanding operationsSum of Queued Operation and Outstanding
Disk|Max Observed OIOMax Observed IO for a disk.
Disk|Highest LatencyHighest Latency.
Disk|Max Queue DepthMaximum queue depth during the collection interval.
perspective of a Guest OS. This is the sum of Kernel
Read Latency and Physical Device Read Latency.
Key: disk|totalReadLatency_average
queue per read.
Key: disk|queueReadLatency_average
physical device.
Key: disk|deviceWriteLatency_average
write.
Key: disk|kernelWriteLatency_average
perspective of a Guest OS. This is the sum of Kernel
Write Latency and Physical Device Write Latency.
Key: disk|totalWriteLatency_average
queue per write.
Key: disk|queueWriteLatency_average
the physical device.
Key: disk|deviceLatency_average
command.
Key: disk|kernelLatency_average
queue per command.
Key: disk|queueLatency_average
Key: disk|diskoio
Key: disk|diskqueued
Key: disk|diskdemand
Operations.
Key: disk|sum_queued_oio
Key: disk|max_observed
Key: disk|maxTotalLatency_latest
Key: disk|maxQueueDepth_average
Key: disk|scsiReservationConicts_summation
38 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
Memory Metrics for Host Systems
Memory metrics provide information about memory use and allocation.
MetricDescription
* Mem|Contention (%)This metric is used to monitor ESXi memory usage.
When the value is high, it means the ESXi is using a
good percentage of available memory. You may need
to add more memory to other memory-related
metrics.
Key: mem|host_contentionPct
Mem|Contention (KB)Host contention in kilobytes.
Key: mem|host_contention
Mem|Host Usage (KB)Machine usage in kilobytes.
Key: mem|host_usage
Mem|Machine Demand (KB)Host demand in kilobytes.
Key: mem|host_demand
Mem|Overall Memory used to run VMs on Host (KB)Overall memory used to run virtual machines on the
host in kilobytes.
Key: mem|host_usageVM
Mem|Provisioned Memory (KB)Provisioned memory in kilobytes.
* Mem|Usage (%)Memory currently in use as a percentage of total
available memory.
Key: mem|host_usagePct
Mem|ESX System UsageMemory usage by the VMkernel and ESX user-level
services.
Key: mem|host_systemUsage
Mem|Guest Active (KB)Amount of memory that is actively used.
Key: mem|active_average
Mem|Consumed (KB)Amount of host memory consumed by the virtual
machine for guest memory.
Key: mem|consumed_average
Mem|Granted (KB)Amount of memory available for use.
Key: mem|granted_average
Mem|Heap (KB)Amount of memory allocated for heap.
Key: mem|heap_average
Mem|Heap Free (KB)Amount of free space in the heap.
Key: mem|heapfree_average
Mem|VM Overhead (KB)Memory overhead reported by host.
Key: mem|overhead_average
Mem|Reserved Capacity (KB)Reserved capacity in kilobytes.
Key: mem|reservedCapacity_average
VMware, Inc. 39
vRealize Operations Definitions for Metrics, Properties, and Alerts
MetricDescription
Mem|Shared (KB)Amount of shared memory in kilobytes.
Mem|Shared Common (KB)Amount of shared common memory in kilobytes.
Mem|Swap In (KB)Amount of memory swapped in.
Mem|Swap Out KB)Amount of memory swapped out.
Mem|Swap Used (KB)Amount of memory used for swapped space in
Mem|VM kernel Usage (KB)Amount of memory used by the VM kernel.
Mem|Unreserved (KB)Amount of unreserved memory in kilobytes.
* Mem|Balloon (KB)This metric shows the total amount of memory
Mem|Zero (KB)Amount of memory that is all zero.
Mem|State (0-3)Overall state of the memory. The value is an integer
Mem|Usage (KB)Host memory use in kilobytes.
Mem|Usage (%)Memory currently in use as a percentage of total
Mem|Swap In Rate (KBps)Rate at which memory is swapped from disk into
Mem|Swap Out Rate (KBps)Rate at which memory is being swapped from active
Key: mem|shared_average
Key: mem|sharedcommon_average
Key: mem|swapin_average
Key: mem|swapout_average
kilobytes.
Key: mem|swapused_average
Key: mem|sysUsage_average
Key: mem|unreserved_average
currently used by the VM memory control. This
memory was reclaimed from the respective VMs at
some point in the past, and was not returned.
Use this metric to monitor how much VM memory
has been reclaimed by ESXi through memory
ballooning.
The presence of ballooning indicates the ESXi has
been under memory pressure. The ESXi activates
ballooning when consumed memory reaches a certain
threshold.
Look for increasing size of ballooning. This indicates
that there has been a shortage of memory more than
once. Look for size uctuations which indicate the
ballooned out page was actually required by the VM.
This translates into a memory performance problem
for the VM requesting the page, since the page must
rst be brought back from the disk.
Key: mem|vmmemctl_average
Key: mem|zero_average
between 0 (high) and 3 (low).
Key: mem|state_latest
Key: mem|host_usage
available memory.
Key: mem|usage_average
active memory during the interval in kilobyte per
second.
Key: mem|swapinRate_average
memory to disk during the current interval in
kilobytes per second.
Key: mem|swapoutRate_average
40 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
MetricDescription
Mem|Active Write (KB)Average active writes in kilobytes.
Key: mem|activewrite_average
Mem|Compressed (KB)Average memory compression in kilobytes.
Key: mem|compressed_average
Mem|Compression Rate (KBps)Average compression rate in kilobytes per second.
Key: mem|compressionRate_average
Mem|Decompression Rate (KBps)Decompression rate in kilobytes per second.
Key: mem|decompressionRate_average
Mem|Total Capacity (KB)Total capacity in kilobytes.
Key: mem|totalCapacity_average
Mem|LatencyPercentage of time the VM is waiting to access
swapped or compressed memory.
Key: mem|latency_average
Mem|Capacity ContentionCapacity Contention.
Key: mem|capacity.contention_average
Mem|Swap In Rate from Host CacheRate at which memory is being swapped from host
cache into active memory.
Key: mem|llSwapInRate_average
Mem|Swap In from Host CacheAmount of memory swapped-in from host cache.
Key: mem|llSwapIn_average
Mem|Swap Out Rate to Host CacheRate at which memory is being swapped to host
cache from active memory.
Key: mem|llSwapOutRate_average
Mem|Swap Out to Host CacheAmount of memory swapped-out to host cache.
Key: mem|llSwapOut_average
Mem|Swap Space Used in Host CacheSpace used for caching swapped pages in the host
cache.
Key: mem|llSwapUsed_average
Mem|Low Free ThresholdThreshold of free host physical memory below which
ESX will begin reclaiming memory from VMs
through ballooning and swapping.
Key: mem|lowfreethreshold_average
Mem|VM Memory Workload DisparityPercentage Memory workload disparity among the
VMs on the Host.
Key: mem|vmWorkloadDisparityPct
Mem|Active Host Load For Balance (Long Term)Active Host Load For Balance (Long Term).
Key: mem|active_longterm_load
Mem|Active Host Load For Balance (Short Term)Active Host Load For Balance (Short Term).
Key: mem|active_shorerm_load
Network Metrics for Host Systems
Network metrics provide information about network performance.
VMware, Inc. 41
vRealize Operations Definitions for Metrics, Properties, and Alerts
MetricDescription
* Net|Packets Received per secondThis metric shows the number of packets received during
* Net|Packets Transmied per secondThis metric shows the number of packets transmied
Net|Packets per secondNumber of packets transmied and received per second.
Net|Usage Rate (KBps)The sum of the data transmied and received for all the
Net|I/O Usage CapacityI/O Usage Capacity.
Net|Max Observed ThroughputMax observed rate of network throughput.
Net|Max Observed Transmied ThroughputMax observed transmied rate of network throughput.
Net|Max Observed Received ThroughputMax observed received rate of network throughput.
Net|Demand (%)Percent demand.
Net|Data Transmit Rate (KBps)Average amount of data transmied per second.
Net|Data Receive Rate (KBps)Average amount of data received per second.
Net|Packets ReceivedNumber of packets received in the performance interval.
Net|Packets TransmiedNumber of packets transmied in the performance
Net|Received Packets DroppedNumber of received packets dropped in the performance
Net|Transmied Packets DroppedNumber of transmied packets dropped in the
* Net|Packets Dropped (%)This metric shows the percentage of received and
Net|Packets DroppedNumber of packets dropped in the performance interval.
Net|bytes Rx (KBps)Average amount of data received per second.
the collection interval.
Use this metric to monitor the network usage of the ESXi.
Key: net|packetsRxPerSec
during the collection interval.
Key: net|packetsTxPerSec
Key: net|packetsPerSec
NIC instances of the host or virtual machine.
Key: net|usage_average
Key: net|usage_capacity
Key: net|maxObserved_KBps
Key: net|maxObserved_Tx_KBps
Key: net|maxObserved_Rx_KBps
Key: net|demand
Key: net|transmied_average
Key: net|received_average
Key: net|packetsRx_summation
interval.
Key: net|packetsTx_summation
interval.
Key: net|droppedRx_summation
performance interval.
Key: net|droppedTx_summation
transmied packets dropped during the collection interval.
This metric is used to monitor reliability and performance
of the ESXi network. When a high value is displayed, the
network is not reliable and performance suers.
Key: net|droppedPct
Key: net|dropped
Key: net|bytesRx_average
42 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
MetricDescription
Net|bytes Tx (KBps)Average amount of data transmied per second.
Key: net|bytesTx_average
Net|Broadcast Packets ReceivedNumber of broadcast packets received during the
sampling interval.
Key: net|broadcastRx_summation
Net|Broadcast Packets TransmiedNumber of broadcast packets transmied during the
sampling interval.
Key: net|broadcastTx_summation
Net|Error Packets ReceivedNumber of packets with errors received.
Key: net|errorsRx_summation
Net|Error Packets TransmiedNumber of packets with errors transmied.
Key: net|errorsTx_summation
Net|Multicast Packets ReceivedNumber of multicast packets received.
Key: net|multicastRx_summation
Net|Multicast Packets TransmiedNumber of multicast packets transmied.
maximum amount. Average value during a ve-minute
period.
Key: sys|resourceCpuMaxLimited5_latest
Key: sys|resourceCpuRun1_latest
Key: sys|resourceCpuRun5_latest
Key: sys|resourceMemAllocMax_latest
Key: sys|resourceMemAllocMin_latest
Key: sys|resourceMemAllocShares_latest
Key: Sys|resourceMemCow_latest
Key: ys|resourceMemMapped_latest
Key: sys|resourceMemOverhead_latest
Key: sys|resourceMemShared_latest
Key: sys|resourceMemSwapped_latest
Key: sys|resourceMemTouched_latest
Key: sys|resourceMemZero_latest
Key: sys|resourceMemConsumed_latest
Key: sys|resourceFdUsage_latest
44 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
MetricDescription
Sys|vMotion Enabled1 if vMotion is enabled or 0 if vMotion is not enabled.
Key: sys|vmotionEnabled
Sys|Not in MaintenanceNot in maintenance.
Key: sys|notInMaintenance
Management Agent Metrics for Host Systems
Management agent metrics provide information about memory use.
MetricDescription
Management Agent|Memory Used (%)Amount of total congured memory that is available for
use.
Key: managementAgent|memUsed_average
Management Agent|Memory Swap Used (KB)Sum of the memory swapped by all powered-on virtual
machines on the host.
Key: managementAgent|swapUsed_average
Management Agent|Memory Swap In (KBps)Amount of memory that is swapped in for the Service
Console.
Key: managementAgent|swapIn_average
Management Agent|Memory Swap Out (KBps)Amount of memory that is swapped out for the Service
Console.
Key: managementAgent|swapOut_average
Management Agent|CPU UsageCPU usage.
Key: managementAgent|cpuUsage_average
Storage Path Metrics for Host Systems
Storage path metrics provide information about data storage use.
MetricDescription
StoragePath|Total Latency (ms)Total latency in milliseconds.
Key: storagePath|totalLatency
StoragePath|Total Usage (KBps)Total latency in kilobytes per second.
Key: storagePath|usage
StoragePath|Read Rate (KBps)Rate of reading data from the virtual disk.
Key: storagePath|read_average
StoragePath|Write Rate (KBps)Rate of writing data.
Key: storagePath|write_average
StoragePath|Commands per secondAverage number of commands issued per second
during the collection interval.
Key: storagePath|commandsAveraged_average
StoragePath|Reads per secondAverage number of read commands issued per second
during the collection interval.
Key: storagePath|numberReadAveraged_average
StoragePath|Writes per secondAverage number of write commands issued per
second during the collection interval.
Key: storagePath|totalWriteLatency_average
VMware, Inc. 45
vRealize Operations Definitions for Metrics, Properties, and Alerts
MetricDescription
StoragePath|Writes per secondAverage number of write commands issued per
StoragePath|Read Latency (ms)Average amount of time for a read operation by the
StoragePath|Highest LatencyHighest Latency.
StoragePath|Storage Path NameStorage path name.
Storage Adapter Metrics for Host Systems
Storage adapter metrics provide information about data storage use.
MetricDescription
Storage Adapter|Total Usage (KBps)Total latency.
Storage Adapter|Port WWNPort World Wide Name.
Storage Adapter|Commands per secondAverage number of commands issued per second by the
Storage Adapter|Reads per secondAverage number of read commands issued per second by the
Storage Adapter|Writes per secondAverage number of write commands issued per second by the
Storage Adapter|Read Rate (KBps)Rate of reading data by the storage adapter.
* Storage Adapter|Read Latency (ms)This metric shows the average amount of time for a read
* Storage Adapter|Write Latency (ms)This metric shows the average amount of time for a write
Storage Adapter|Write Rate (KBps)Rate of writing data by the storage adapter.
Storage Adapter|DemandDemand.
second during the collection interval.
Key: storagePath|numberWriteAveraged_average
storage adapter.
Key: storagePath|totalReadLatency_average
Key: storagePath|maxTotalLatency_latest
Key: storagePath|storagePathName
Key: storageAdapter|usage
Key: storageAdapter|portWWN
storage adapter during the collection interval.
Key: storageAdapter|commandsAveraged_average
storage adapter during the collection interval.
Key: storageAdapter|numberReadAveraged_average
storage adapter during the collection interval.
Key: storageAdapter|numberWriteAveraged_average
Key: storageAdapter|read_average
operation by the storage adapter.
Use this metric to monitor the storage adapter read operation
performance. A high value means that the ESXi is performing
a slow storage read operation.
Total latency is the sum of kernel latency and device latency.
Key: storageAdapter|totalReadLatency_average
operation by the storage adapter.
Use this metric to monitor the storage adapter write
performance operation. A high value means that the ESXi is
performing a slow storage write operation.
Total latency is the sum of kernel latency and device latency.
Key: storageAdapter|totalWriteLatency_average
Key: storageAdapter|write_average
Key: storageAdapter|demand
46 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
Storage Adapter|Queue Command Latency (ms)The average time spent in the ESX Server VM Kernel queue
per command.
Key: storageAdapter|queueLatency_average
Storage Adapter|QueuedQueued.
Key: storageAdapter|queued_average
Storage Metrics for Host Systems
Storage metrics provide information about storage use.
MetricDescription
Storage|Commands per secondAverage number of commands issued per second
during the collection interval.
Key: storage|commandsAveraged_average
Storage|Read Latency (ms)Average amount of time for a read operation in
milliseconds.
Key: storage|totalReadLatency_average
Storage|Read Rate (KBps)Read throughput rate in kilobytes.
Key: storage|read_average
Storage|Reads per secondAverage number of read commands issued per
second during the collection interval.
Key: storage|numberReadAveraged_average
Storage|Total Latency (ms)Total latency in milliseconds.
Key: storage|totalLatency_average
Storage|Total Usage (KBps)Total throughput rate in kilobytes per second.
Key: storage|usage_average
Storage|Write Latency (ms)Average amount of time for a write operation in
milliseconds.
Key: storage|totalWriteLatency_average
Storage|Write Rate (KBps)Write throughput rate in kilobytes per second.
Key: storage|write_average
Storage|Writes per secondAverage number of write commands issued per
second during the collection interval.
Key: storage|numberWriteAveraged_average
Sensor Metrics for Host Systems
Sensor metrics provide information about host system cooling.
VMware, Inc. 47
vRealize Operations Definitions for Metrics, Properties, and Alerts
MetricDescription
Sensor|Fan|Speed (%)Percent fan speed.
Sensor|Fan|Health StateFan health state.
Sensor|Temperature|Temp CFan temperature in centigrade.
Sensor|Temperature|Health StateFan health state.
Power Metrics for Host Systems
Power metrics provide information about host system power use.
MetricDescription
Power|Energy (Joule)Host power use in joules.
Power|Power (Wa)Host power use in was.
Power|Power Cap (Wa)Host power capacity in was.
Key: Sensor|fan|currentValue
Key: Sensor|fan|healthState
Key: Sensor|temperature|currentValue
Key: Sensor|temperature|healthState
Key: power|energy_summation
Key: power|power_average
Key: power|powerCap_average
Disk Space Metrics for Host Systems
Disk space metrics provide information about disk space use.
MetricDescription
Diskspace|Not Shared (GB)Unshared disk space in gigabytes.
Key: diskspace|notshared
Diskspace|Number of Virtual DisksNumber of virtual disks.
Key: diskspace|numvmdisk
Diskspace|Shared Used (GB)Used shared disk space in gigabytes.
Key: diskspace|shared
Diskspace|SnapshotDisk space used by snapshots in gigabytes.
Key: diskspace|snapshot
Diskspace|Virtual Disk Used (GB)Disk space used by virtual disks in gigabytes.
Key: diskspace|diskused
Diskspace|Virtual machine used (GB)Disk space used by virtual machines in gigabytes.
Key: diskspace|used
Diskspace|tTotal disk space usedTotal disk space used on all datastores visible to this object.
Key: diskspace|total_usage
Diskspace|Total disk spaceyTotal disk space on all datastores visible to this object.
Key: diskspace|total_capacity
Diskspace|Total provisioned disk spaceTotal provisioned disk space on all datastores visible to this object.
Key: diskspace|total_provisioned .
Summary Metrics for Host Systems
Summary metrics provide information about overall host system performance.
48 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
MetricDescription
* Summary|Number of Running VMsThis metric shows the number of VMs running on the host
during the last metric collection time.
Large spikes of running VMs might be a reason for CPU or
memory spikes as more resources will be used in the host.
Number of Running VMs gives you a good indicator of how
many requests the ESXi host must juggle. This excludes
powered o VMs as they do not impact ESXi performance. A
change in this number in your environment can contribute to
performance problems. A high number of running VMs in a
host also means a higher concentration risk, as all the VMs
will go down (or be relocated by HA) if the ESXi crashes.
Look for any correlation between spikes in the number of
running VMs and spikes in other metrics such as CPU
Contention/Memory Contention.
Key: summary|number_running_vms
Summary|Maximum Number of VMsMaximum number of virtual machines
Key: summary|max_number_vms
* Summary|Number of vMotionsThis metric shows the number of vMotions that occurred in
the host in the last X minutes.
The number of vMotions is a good indicator of stability. In a
healthy environment, this number should be stable and
relatively low.
Look for correlation between vMotions and spikes in other
metrics such as CPU/Memory contention.
The vMotion should not create any spikes, however, the VMs
moved into the host might create spikes in memory usage,
contention and CPU demand and contention.
Key: summary|number_vmotion
Summary|Total Number of DatastoresTotal Number of Datastores.
Key: summary|total_number_datastores
Summary|Number of VCPUs on Powered On VMsTotal number of VCPUs of Virtual Machines that are powered
on.
Key: summary|number_running_vcpus
Summary|Total Number of VMsTotal number of virtual machines.
Storage metrics provide information about storage use.
MetricDescription
Storage|Total UsageTotal throughput rate in kilobytes per second.
Key: storage|usage_average
Disk Space Metrics for Cluster Compute Resources
Disk space metrics provide information about disk space use.
MetricDescription
Diskspace|Virtual machine used (GB)Space used by virtual machine les in gigabytes.
Key: diskspace|used
Diskspace|Total disk space usedTotal disk space used on all datastores visible to this object.
Key: diskspace|total_usage
Diskspace|Total disk spaceTotal disk space on all datastores visible to this object.
Key: diskspace|total_capacity
50 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
MetricDescription
Diskspace|Total provisioned disk spaceTotal provisioned disk space on all datastores visible to this object.
Key: diskspace|total_provisioned
Diskspace|Virtual Disk Used (GB)Space used by virtual disks in gigabytes.
Key: diskspace|diskused
Diskspace|Snapshot Space (GB)Space used by snapshots in gigabytes.
Key: diskspace|snapshot
Diskspace|Shared Used (GB)Shared used space in gigabytes.
Key: diskspace|shared
Diskspace|Not Shared (GB)Space used by VMs that is not shared.
Key: diskspace|notshared
CPU Usage Metrics for Cluster Compute Resources
CPU usage metrics provide information about CPU use.
MetricDescription
CPU|Capacity UsageThis metric shows the percentage of the capacity used.
Key: cpu|capacity_usagepct_average
* CPU|CPU Contention (%)This metric is an indicator of the overall contention for CPU
resources that occurs across the workloads in the cluster. When
contention occurs, it means that some of the virtual machines are
not immediately geing the CPU resources they are requesting.
Use this metric to identify when a lack of CPU resources might be
causing performance issues in the cluster.
This metric is the sum of the CPU contention across all hosts in the
cluster averaged over two times the number of physical CPUs in the
cluster to account for hyper-threading. CPU contention takes into
account:
CPU Ready
n
CPU Co-stop
n
Power management
n
Hyper threading
n
This metric is more accurate than CPU Ready since it takes into
account CPU Co-stop and Hyper threading.
When using this metric, the number should be lower than the
performance you expect. If you expect performance at 10%, then the
number should be lower than 10%.
Since this value is averaged across all hosts in the cluster, you may
nd that some hosts have a higher CPU contention while others are
lower. In order to ensure that vSphere spreads out the running
workloads across hosts, consider enabling a fully-automated DRS in
the cluster.
Key: cpu|capacity_contentionPct
* CPU|Demand (%)This metric is an indicator of the overall demand for CPU resources
by the workloads in the cluster.
It shows the percentage of CPU resources that all the virtual
machines would use if there were no CPU contention or CPU limits
set. It represents the average active CPU load in the past ve
minutes.
Key: cpu|demandPct
CPU|Demand (MHz)Demand in megaher.
Key: cpu|demandmhz
VMware, Inc. 51
vRealize Operations Definitions for Metrics, Properties, and Alerts
MetricDescription
CPU|IO WaitIO wait time in milliseconds.
CPU|Number of CPU SocketsNumber of CPU sockets.
CPU|Overall CPU ContentionOverall CPU contention in milliseconds.
CPU|Host Provisioned CapacityProvisioned CPU capacity in megaher.
CPU|Provisioned vCPUsNumber of provisioned CPU cores.
CPU|Reserved CapacityThe sum of the reservation properties of the (immediate) children of
CPU|WaitCPU time spent on idle state in milliseconds.
CPU|Usage (MHz)Average CPU use in megaher.
CPU|Total CapacityTotal CPU capacity in megaher.
CPU|DemandCPU Demand.
CPU|OverheadAmount of CPU overhead.
CPU|Demand without overheadValue of demand excluding any overhead.
CPU|Host workload Max-Min DisparityDierence of Max and Min host workload in the container.
CPU|Host stress Max-Min DisparityDierence of Max and Min host stress in the container.
Key: cpu|iowait
Key: cpu|numpackages
Key: cpu|capacity_contention
Key: cpu|capacity_provisioned
Key: cpu|corecount_provisioned
the host's root resource pool in megaher.
Key: cpu|reservedCapacity_average
Key: cpu|wait
Key: cpu|usagemhz_average
Key: cpu|totalCapacity _average
Key: cpu|demand_average
Key: cpu|overhead_average
Key: cpu|demand_without_overhead
Key: cpu|vm_capacity_provisioned
Key: cpu|num_hosts_stressed
Key: cpu|stress_balance_factor
Key: cpu|min_host_capacity_remaining
Key: cpu|workload_balance_factor
Key: cpu|max_host_workload
Key: cpu|host_workload_disparity
Key: cpu|host_stress_disparity
Disk Metrics for Cluster Compute Resources
Disk metrics provide information about disk use.
52 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
MetricDescription
Disk|Commands per secondAverage number of commands issued per second during the
collection interval.
Key: disk|commandsAveraged_average
Disk|Disk Command Latency (ms)Average amount of time taken for a command from the
perspective of the guest operating system. This metric is the sum
of the Kernel Command Latency and Physical Device Command
Latency metrics.
Key: disk|totalLatency_average
Disk|Disk Read LatencyAverage amount of time for a read operation from the virtual
disk. The total latency is the sum of Kernel latency and device
latency.
Key: disk|totalReadLatency_average
Disk|Disk Write LatencyThe average amount of time taken for a read from the perspective
of a Guest OS. This is the sum of Kernel Read Latency and
Physical Device Read Latency.
Key: disk|totalWriteLatency_averag
Disk|Read Rate (KBps)Number of times data was read from the disk in the dened
interval.
Key: disk|numberRead_summation
Disk|Reads per secondAverage number of read commands issued per second during the
collection interval.
Key: disk|numberReadAveraged_averag
Disk|Usage Rate (KBps)Average of the sum of the data read and wrien for all of the disk
instances of the host or virtual machine.
Key: disk|usage_average
Disk|Write Rate (KBps)Number of times data was wrien to disk during the collection
interval.
Key: disk|numberWrite_summation
Disk|Writes per secondAverage number of write commands issued per second during
the collection interval.
Key: disk|numberWriteAveraged_average
Disk|Read RequestsAmount of data read from the disk during the collection interval.
Key: disk|read_average
Disk|Write RequestsAmount of data wrien to the disk during the collection interval.
Key: disk|write_average
Disk|Commands IssuedNumber of disk commands issued during the collection interval.
Key: disk|commands_summation
Disk|Total Queued Outstanding operationsSum of queued operation and outstanding operations.
Key: disk|sum_queued_oio
Disk|Max Observed OIOMax observed outstanding IO for a disk.
Key: disk|max_observed
Memory Metrics for Cluster Compute Resources
Memory metrics provide information about memory use and allocation.
VMware, Inc. 53
vRealize Operations Definitions for Metrics, Properties, and Alerts
MetricDescription
Mem|Active Write (KB)Active writes in kilobytes.
Mem|Compressed (KB)Average compression in kilobytes.
Mem|Compression Rate (KBps)Average compression rate in kilobytes.
Mem|Consumed (KB)Amount of host memory consumed by the virtual machine for
* Mem|Contention (%)This metric is an indicator of the overall contention for memory
Mem|Contention (KB)Contention in kilobytes.
Mem|Decompression Rate (KBpsDecompression rate in kilobytes.
Mem|Granted (KB)Amount of memory available for use.
Mem|Guest Active (KB)Amount of memory that is actively used.
Mem|Heap (KB)Amount of memory allocated for heap.
Mem|Heap Free (KB)Free space in the heap.
* Mem|BalloonThis metric shows the amount of memory currently used by the
Mem|VM Overhead (KB)Memory overhead reported by host.
Mem|Provisioned Memory (KB)Provisioned memory in kilobytes.
Mem|Reserved Capacity (KB)Reserved capacity in kilobytes.
Mem|Shared (KB)Amount of shared memory.
Mem|Shared Common (KB)Amount of shared common memory.
Mem|Swap In (KB)Amount of memory that is swapped in for the service console.
Mem|Swap In Rate (KBps)Rate at which memory is swapped from disk into active memory
Key: mem|activewrite_average
Key: mem|compressed_average
Key: mem|compressionRate_average
guest memory.
Key: mem|consumed_average
resources that occurs across the workloads in the cluster. When
contention occurs, it means that some portion of the VMs are not
immediately geing the memory resources that they are
requesting.
Use this metric to identify when lack of memory resources might
be causing performance issues in the cluster.
Key: mem|host_contentionPct
Key: mem|host_contention
Key: mem|decompressionRate_average
Key: mem|granted_average
Key: mem|active_average
Key: mem|heap_average
Key: mem|heapfree_average
virtual machine memory control. It is only dened at the VM
level.
Key: mem|vmmemctl_average
Key: mem|overhead_average
Key: mem|host_provisioned
Key: mem|reservedCapacity_average
Key: mem|shared_average
Key: mem|sharedcommon_average
Key: mem|swapin_average
during the interval.
Key: mem|swapinRate_average
54 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
MetricDescription
Mem|Swap Out (KB)Amount of memory that is swapped out for the service console.
Key: mem|swapout_average
Mem|Swap Out Rate (KBps)Rate at which memory is being swapped from active memory
into disk during the current interval.
Key: mem|swapoutRate_average
Mem|Swap Used (KB)Amount of memory used for swap space.
Key: mem|swapused_average
Mem|Total Capacity (KB)Total capacity in kilobytes.
Key: mem|totalCapacity_average
Mem|Reserved (KB)Amount of unreserved memory.
Key: mem|unreserved_average
Mem|Usable Memory (KB)Usable memory in kilobytes.
Key: mem|host_usable
Mem|Usage/UsablePercent memory used.
Key: mem|host_usagePct
Mem|Host Usage (KB)Memory use in kilobytes.
Key: mem|host_usage
Mem|Machine DemandMemory Machine Demand in KB.
Key: mem|host_demand
Mem|ESX System UsageMemory usage by the VMkernel and ESX user-level services.
Key: mem|host_systemUsage
* Mem|Usage (%)This metric shows the portion of the total memory in all hosts in
the cluster that is being used.
This metric is the sum of memory consumed across all hosts in
the cluster divided by the sum of physical memory across all
hosts in the cluster.
∑ memory consumed on all hosts
--------------------------------------------- X 100%
∑ physical memory on all hosts
Mem|Usage (KB)Memory currently in use as a percentage of total available
memory.
Key: mem|usage_average
Mem|VM kernel Usage (KB)Amount of memory that the VM kernel uses.
Key: mem|sysUsage_average
Mem|Zero (KB)Amount of memory that is all 0.
Key: mem|zero_average
Mem|Number of Hosts StressedNumber of hosts stressed.
Summary|Total Number of DatastoresTotal number of datastores.
Summary|Number of VCPUs on Powered On VMsNumber of virtual CPUs on powered-on virtual
Summary|Average Running VM Count per Running HostAverage number of running virtual machines per
Summary|Average Provisioned Capacity (MHz) per Running
VM
Summary|Average Provisioned Memory (KB) per Running VMAverage provisioned memory, in kilobytes. per
Key: summary|number_running_hosts
on all hosts in the cluster.
Key: summary|number_running_vms
occurred during the last collection cycle.
When using this metric, look for a low number which
indicates that the cluster is able to serve its VMs. A
vMotion can impact VM performance during the stun
time.
Key: summary|number_vmotion
Key: summary|total_number_hosts
Key: summary|total_number_vms
Key: summary|max_number_vms
Key: summary|workload_indicator
Key: summary|total_number_datastores
machines.
Key: summary|number_running_vcpus
running host.
Key: summary|avg_vm_density
Average provisioned capacity, in megaher, per
running virtual machine.
Key: summary|avg_vm_cpu
running virtual machine.
Key: summary|avg_vm_mem
Resource Pool Metrics
vRealize Operations Manager collects conguration, CPU usage, memory, and summary metrics for
resource pool objects.
Resource Pool metrics include capacity and badge metrics. See denitions in:
“Capacity and Project-Based Metrics,” on page 77
n
“Badge Metrics,” on page 80
n
Configuration Metrics for Resource Pools
Conguration metrics provide information about memory and CPU allocation conguration.
58 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
Table 1‑14. Configuration Metrics for Resource Pools
cpu|host_workload_disparityHost workload Max-Min DisparityDierence of Max and Min host
cpu|host_stress_disparityHost stress Max-Min DisparityDierence of Max and Min host stress in
Lowest Provider Capacity Remaining.
workload in the container.
the container.
Disk Metrics for Datacenters
Disk metrics provide information about disk use.
Table 1‑19. Disk Metrics for Datacenters
Metric KeyMetric NameDescription
disk|commandsAveraged_averageCommands per secondAverage number of commands issued
per second during the collection
interval.
disk|totalLatency_averageDisk Command Latency (ms)Average amount of time taken for a
command from the perspective of the
guest operating system. This metric is
the sum of the Kernel Disk Command
Latency and Physical Device Command
Latency metrics.
VMware, Inc. 61
vRealize Operations Definitions for Metrics, Properties, and Alerts
Table 1‑19. Disk Metrics for Datacenters (Continued)
Metric KeyMetric NameDescription
disk|usage_averageUsage Rate (KBps)Average of the sum of the data read and
disk|sum_queued_oioTotal queued outstanding operationsSum of queued operations and
disk|max_observedMax observed OIOMax observed IO for a disk.
Memory Metrics for Datacenters
Memory metrics provide information about memory use and allocation.
Chapter 1 Metric Definitions in vRealize Operations Manager
Table 1‑35. Host Metrics for VMware Distributed Virtual Switches (Continued)
Metric KeyMetric NameDescription
host|cong_outofsyncCong Out Of SyncCong Out Of Sync.
host|aached_pnicsNumber of Aached pNICsNumber of aached physical NICs.
Distributed Virtual Port Group Metrics
The vCenter Adapter instance collects network and summary metrics for distributed virtual port groups.
Distributed Virtual Port Group metrics include capacity and badge metrics. See denitions in:
“Capacity and Project-Based Metrics,” on page 77
n
“Badge Metrics,” on page 80
n
Table 1‑36. Network Metrics for Distributed Virtual Port Groups
Metric KeyMetric NameDescription
network|port_statistics|
rx_bytes
network|port_statistics|
tx_bytes
network|port_statistics|
ucast_tx_pkts
network|port_statistics|
mcast_tx_pkts
network|port_statistics|
bcast_tx_pkts
network|port_statistics|
ucast_rx_pkts
network|port_statistics|
mcast_rx_pkts
network|port_statistics|
bcast_rx_pkts
network|port_statistics|
dropped_tx_pkts
network|port_statistics|
dropped_rx_pkts
network|port_statistics|rx_pktsTotal Ingress Packets per secondTotal Ingress packets per second.
network|port_statistics|tx_pktsTotal Egress Packets per secondTotal Egress packets per second.
network|port_statistics|
utilization
network|port_statistics|
dropped_pkts
network|port_statistics|
dropped_pkts_pct
network|port_statistics|
maxObserved_rx_bytes
network|port_statistics|
maxObserved_tx_bytes
network|port_statistics|
maxObserved_utilization
Ingress TracIngress trac (KBps).
Egress TracEgress trac (KBps).
Egress Unicast Packets per secondEgress unicast packets per second.
Egress Multicast Packets per secondEgress multicast packets per second.
Egress Broadcast Packets per secondEgress broadcast packets per second.
Ingress Unicast Packets per secondIngress unicast packets per second.
Ingress Multicast Packets per secondIngress multicast packets per second.
Ingress Broadcast Packets per secondIngress broadcast packets per second.
Egress Dropped Packets per secondEgress dropped packets per second.
Ingress Dropped Packets per secondIngress dropped packets per second.
UtilizationUtilization (KBps).
Total Dropped Packets per secondTotal dropped packets per second.
Percentage of Dropped PacketsPercentage of dropped packets.
Max Observed Ingress Trac (KBps)Max observed ingress trac (KBps).
Max Observed Egress Trac (KBps)Max observed egress trac (KBps).
Max Observed Utilization (KBps)Max observed utilization (KBps).
VMware, Inc. 69
vRealize Operations Definitions for Metrics, Properties, and Alerts
Table 1‑37. Summary Metrics for Distributed Virtual Port Groups
Metric KeyMetric NameDescription
summary|max_num_portsMaximum Number of PortsMaximum number of ports.
summary|used_num_portsUsed Number of PortsUsed number of ports.
summary|num_blocked_portsNumber of Blocked PortsNumber of blocked ports.
Datastore Metrics
vRealize Operations Manager collects capacity, device, and summary metrics for datastore objects.
Capacity metrics can be calculated for datastore objects. See “Capacity and Project-Based Metrics,” on
page 77.
Metrics marked with an asterisk (*) provide the most relevant data to use when you troubleshoot the
datastores in your environment.
Capacity Metrics for Datastores
Capacity metrics provide information about datastore capacity.
MetricDescription
* Capacity|Available Space (GB)This metric shows the amount of free space that a datastore has
Capacity|Data Store Capacity ContentionDatastore capacity contention.
* Capacity|Provisioned (GB)This metric shows the amount of storage that was allocated to
* Capacity|Total Capacity (GB)This metric shows the overall size of the datastore.
Capacity|Used Space (GB)This metric shows the amount of storage that is being used on
Capacity|Workload (%)Capacity workload.
Capacity|Uncommied Space (GB)Uncommied space in gigabytes.
available.
Use this metric to know how much storage space is unused on
the datastore. Try to avoid having too lile free disk space in
order to accommodate unexpected storage growth on the
datastore. The exact size of the datastore is based on company
policy.
Key: capacity|available_space
Key: capacity|contention
the virtual machines.
Use this metric to know how much storage space is currently
being used on the datastore.
Check the metric trend to identify spikes or abnormal growth.
Key: capacity|provisioned
Use this metric to know the total capacity of the datastore.
Typically the size of the datastore should not be too small. VMFS
datastore size has grown over the years as virtualization matures
and larger vitual machines are now onboard. Ensure the size can
handle enough virtual machines to avoid datastore sprawl. A
best practise is to use 5 TB for VMFS and more for vSAN.
Key: capacity|total_capacity
the datastore.
Key: capacity|used_space
Key: capacity|workload
Key: capacity|uncommied
70 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
* Capacity|Used Space (%)This metric shows the amount of storage that is being used on
the datastore.
Use this metric to know the percentage of storage space being
used on the datastore.
When using this metric, verify that you have at least 20% of free
storage. Less than this, and you may experience problems when
a snapshot is not deleted. If you have more than 50% free storage
space, you are not utilizing your storage in the best possible way.
Key: capacity|usedSpacePct
Device Metrics for Datastores
Device metrics provide information about device performance.
MetricDescription
Devices|Bus ResetsThis metric shows the number of bus resets in the
performance interval.
Key: devices|busResets_summation
Devices|Commands AbortedThis metric shows the number of disk commands aborted
in the performance interval.
Key: devices|commandsAborted_summation
Devices|Commands IssuedThis metric shows the number of disk commands issued
in the performance interval.
Key: devices|commands_summation
Devices|Disk Command Latency (ms)This metric shows the average time taken for a command
from the perspective of a guest operating system. This
metric is the sum of Kernel Disk Command Latency and
Physical Device Command Latency metrics.
Key: devices|totalLatency_average
Devices|Disk Read Latency (ms)This metric shows the average time taken for a read from
the perspective of a guest operating system. This metric is
the sum of the Kernel Disk Read Latency and Physical
Device Read Latency metrics.
Key: devices|totalReadLatency_averag
Devices|Disk Write Latency (ms)This metric shows the average amount of time for a write
operation to the datastore. Total latency is the sum of
kernel latency and device latency.
Key: devices|totalWriteLatency_average
Devices|Kernel Disk Command Latency (ms)Average time spent in ESX Server V. Kernel per command.
Key: devices|kernelLatency_average
Devices|Kernel Disk Read Latency (ms)Average time spent in ESX host VM Kernel per read.
Key: devices|kernelReadLatency_average
Devices|Kernel Disk Write Latency (ms)Average time spent in ESX Server VM Kernel per write.
Key: devices|kernelWriteLatency_average
Devices|Number of Running HostsNumber of running hosts that are powered on.
Key: devices|number_running_hosts
Devices|Number of Running VMsNumber of running virtual machines that are powered on.
Key: devices|number_running_vms
VMware, Inc. 71
vRealize Operations Definitions for Metrics, Properties, and Alerts
MetricDescription
Devices|Physical Device Command Latency (ms)Average time taken to complete a command from the
Devices|Physical Device Read Latency (ms)Average time taken to complete a read from the physical
Devices|Queue Command Latency (ms)Average time spent in the ESX Server VM Kernel queue
Devices|Queue Read Latency (ms)Average time spent in the ESX Server VM Kernel queue
Devices|Queue Write Latency (ms)Average time spent in the ESX Server VM Kernel queue
Devices|Read Rate (KBps)Amount of data read in the performance interval.
Devices|Read RequestsNumber of times data was read from the disk in the
Devices|Reads per secondAverage number of read commands issued per second to
Devices|Usage Average (KBps)Average use in kilobytes per second.
Devices|Write Rate (KBps)Amount of data wrien to disk in the performance
Devices|Write RequestsNumber of times data was wrien to the disk in the
Devices|Writes per secondAverage number of write commands issued per second to
Devices|Commands per secondAverage number of commands issued per second during
Devices|Physical Device Write Latency (ms)Average time taken to complete a write from the physical
physical device.
Key: devices|deviceLatency_average
device.
Key: devices|deviceReadLatency_average
per command.
Key: devices|queueLatency_average
per read.
Key: devices|queueReadLatency_average
per write.
Key: devices|queueWriteLatency_average
Key: devices|read_average
dened interval.
Key: devices|numberRead_summation
the datastore during the collection interval.
Key: devices|numberReadAveraged_average
Key: devices|usage_average
interval.
Key: devices|write_average
dened interval.
Key: devices|numberWrite_summation
the datastore during the collection interval.
Key: devices|numberWriteAveraged_average
the collection interval.
Key: devices|commandsAveraged_average
disk.
Key: devices|deviceWriteLatency_average
Datastore Metrics for Datastores
Datastore metrics provide information about datastore use.
72 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
MetricDescription
* Datastore|Disk Command Latency (ms)This metric shows the adjusted read and write latency
at the datastore level. Adjusted means that the latency
is taking into account the number of IOs. If your IO is
read-dominated, the combined value is inuenced by
the reads.
This is the average of all the VMs running in the
datastore. Because it is an average, some VMs logically
experience higher latency that the value shown by this
metric. To see the worst latency experienced by any
VM, use the Maximum VM Disk Latency metric.
Use this metric to see the performance of the datastore.
It is one of two key performance indicators for a
datastore, the other being the Max Read Latency. The
combination of Maximum and Average gives beer
insight into how well the datastore is coping with the
demand.
The number should be lower than the performance you
expect.
Key: datastore|totalLatency_average
Datastore|Usage Average (KBps)Average use in kilobytes per second.
Key: datastore|usage_average
Datastore|Read Latency (msAverage amount of time for a read operation from the
datastore. Total latency = kernel latency + device
latency.
Key: datastore|totalReadLatency_average
* Datastore|Write Latency (ms)Average amount of time for a write operation to the
datastore. Total latency = kernel latency + device
latency.
Key: datastore|totalWriteLatency_average
Datastore|DemandDemand.
Key: datastore|demand
Datastore|Demand IndicatorDemand Indicator.
Key: datastore|demand_indicator
Datastore|Max Observed Reads per SecondMaximum observed average number of read
commands issued per second during the collection
interval.
Key: datastore|maxObserved_NumberRead
Datastore|Max Observed Read Rate (KBps)Max observed rate of reading data from the datastore.
Key: datastore|maxObserved_Read
* Datastore|Max Observed Read Latency (ms)This metric displays the maximum observed average
amount of time for a read operation from the datastore.
Use this metric to troubleshoot when the overall
datastore latency is higher than expected. Look for a
number that matches the overall latency.
Total latency = kernel latency + device latency.
Key: datastore|maxObserved_ReadLatency
Datastore|Max Observed Writes per secondMax observed average number of write commands
issued per second during the collection interval.
Key: datastore|maxObserved_NumberWrite
Datastore|Max Observed Write Rate (KBps)Max observed rate of writing data from the datastore.
Key: datastore|maxObserved_Write
VMware, Inc. 73
vRealize Operations Definitions for Metrics, Properties, and Alerts
MetricDescription
Datastore|Max Observed Write Latency (ms)This metric displays the maximum observed average
Datastore|Max Observed Number of Outstanding IO
Operations
Datastore|Outstanding IO requestsOIO for datastore.
* Datastore|Reads per second (IOPS)This metric displays the average number of read
* Datastore|Writes per second (IOPS)This metric displays the average number of write
Datastore|Read rateThis metric displays the amount of data read in the
Datastore|Write rateThis metric displays the amount of data wrien to disk
amount of time for a write operation from the
datastore.
Use this metric to troubleshoot when the overall
datastore latency is higher than expected. Look for a
number that matches the overall latency.
Total latency = kernel latency + device latency.
Key: datastore|maxObserved_WriteLatency
Maximum observed number of outstanding IO
operations.
Key: datastore|maxObserved_OIO
Key: datastore|demand_oio
commands issued per second during the collection
interval.
Use this metric when the total IOPS is higher than
expected. Drill down to see if the metric is read or write
dominated. This helps determine the cause of the high
IOPS. Certain workloads such as backups, anti-virus
scans, and Windows updates carry a Read/Write
paern. For example, an anti-virus scan is heavy on
read since it is mostly reading the le system.
Key: datastore|numberReadAveraged_average
commands issued per second during the collection
interval.
Use this metric when the total IOPS is higher than
expected. Drill down to see if the metric is read or write
dominated. This helps determine the cause of the high
IOPS. Certain workloads such as backups, anti-virus
scans, and Windows updates carry a Read/Write
paern. For example, an anti-virus scan is heavy on
read since it is mostly reading the le system.
Key: datastore|numberWriteAveraged_average
performance interval.
Key: datastore|read_average
in the performance interval.
Key: datastore|write_average
About Datastore Metrics for Virtual SAN
The metric named datastore|oio|workload is not supported on Virtual SAN datastores. This metric
depends on datastore|demand_oio, which is supported for Virtual SAN datastores.
The metric named datastore|demand_oio also depends on several other metrics for Virtual SAN datastores,
one of which is not supported.
The metrics named devices|numberReadAveraged_average and devices|numberWriteAveraged_average
n
are supported.
The metric named devices|totalLatency_average is not supported.
n
As a result, vRealize Operations Manager does not collect the metric named datastore|oio|workload for
Virtual SAN datastores.
74 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
Disk Space Metrics for Datastores
Disk space metrics provide information about disk space use.
MetricDescription
Diskspace|Not Shared (GB)Unshared space in gigabytes.
Key: diskspace|notshared
Diskspace|Number of Virtual DiskNumber of virtual disks.
Key: diskspace|numvmdisk
Diskspace|Provisioned Space (GB)Provisioned space in gigabytes.
Key: diskspace|provisioned
Diskspace|Shared Used (GB)Shared used space in gigabytes.
Key: diskspace|shared
* Diskspace|Snapshot Space (GB)This metric shows the amount of space taken by snapshots
on a given database.
Use this metric to know how much storage space is being
used by virtual machine snapshots on the datastore.
Check that the snapshot is using 0 GB or minimal space.
Anything over 1 GB should trigger a warning. The actual
value depends on how IO intensive the virtual machines in
the datastore are. Run a DT on them to detect anomaly.
Clear the snapshot within 24 hours, preferably as soon as
you have nished backing up, or patching.
Key: diskspace|snapshot
Diskspace|Virtual Disk Used (GB)Virtual disk used space in gigabytes.
Key: diskspace|diskused
Diskspace|Virtual machine used (GB)Virtual machine used space in gigabytes.
Key: diskspace|used
Diskspace|Total disk space usedTotal disk space used on all datastores visible to this object.
Key: diskspace|total_usage
Diskspace|Total disk spaceTotal disk space on all datastores visible to this object.
Key: diskspace|total_capacity
Diskspace|Total provisioned disk spaceTotal provisioned disk space on all datastores visible to
this object.
Key: diskspace|total_provisioned
Diskspace|Total used (GB)Total used space in gigabytes.
Key: diskspace|disktotal
Diskspace|Swap File Space (GB)Swap le space in gigabytes.
Key: diskspace|swap
Diskspace|Other VM Space (GB)Other virtual machine space in gigabytes.
Key: diskspace|otherused
Diskspace|Freespace (GB)Unused space available on datastore.
Key: diskspace|freespace
Diskspace|Capacity (GB)Total capacity of datastore in gigabytes.
Key: diskspace|capacity
Diskspace|OverheadAmount of disk space that is overhead.
Key: diskspace|overhead
VMware, Inc. 75
vRealize Operations Definitions for Metrics, Properties, and Alerts
Summary Metrics for Datastores
Summary metrics provide information about overall performance.
MetricDescription
* Summary|Total Number of HostsThis metric shows the number of hosts that the datastore is
* Summary|Total Number of VMsThis metric shows the number of virtual machines which
Summary|Maximum Number of VMsMaximum number of virtual machines.
Summary|Workload IndicatorWorkload indicator.
* Summary|Total Number of ClustersThis metric shows the number of clusters that the datastore
connected to.
Use this metric to know how many clusters the datastore is
aached to.
The number should not be too high, as a datastore should
not be mounted by every host. The datastore and cluster
should be paired to keep operations simple.
Key: summary|total_number_hosts
save their VMDK les on the datastore. If a VM has four
VMDKs stored in four datastores, the VM will be counted
on each datastore.
Use this metric to know how many VMs have at least one
VMDK on a specic datastore.
The number of VMs should be within your Concentration
Risk policy.
You should also expect the datastore to be well used. If only
a few VMs are using the datastore, this is not considered a
good use.
Key: summary|total_number_vms
Key: summary|max_number_vms
Key: summary|workload_indicator
is connected to.
Key: summary|total_number_clusters
Template Metrics for Datastores
MetricDescription
Template|Virtual Machine usedSpace used by virtual machine les.
Key: template|used
Template|Access TimeLast access time.
Key: template|accessTime
Calculated Metrics
vRealize Operations Manager calculates metrics for capacity, badges, and the health of the system.
Calculated metrics apply to a subset of objects found in the describe.xmlle that describes each adapter.
From data that the vCenter adapter collects, vRealize Operations Manager calculates metrics for objects of
type:
vSphere World
n
Virtual Machine
n
Host System
n
76 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
Datastore
n
From data that the vRealize Operations Manager adapter collects, vRealize Operations Manager calculates
metrics for objects of type:
Node
n
Cluster
n
Capacity and Project-Based Metrics
The capacity engine computes and publishes metrics that help you to plan your resource use based on
consumer demand. Project-based metrics are a subset of capacity metrics that help to plan future resource
use based on predicted consumer demand.
Capacity Metrics Group
For the capacity metrics group, full metric names include the name of the resource container. For example, if
density metrics are computed for CPU or memory, the actual metric names appear as cpu|density or mem|
density.
Only resource containers enabled for the capacity computations have relevant metrics. Not all metric types
are generated for all resource containers. For example, if CPU or memory resource containers are enabled in
a policy for density, but the network resource container is not, then cpu|density and mem|density metrics
are calculated but network|density metrics are not.
A capacity metric denition includes resource containers that act as a consumer or a provider. For example
in vSphere, the virtual machines are consumers of CPU and memory that the ESX host provides.
Table 1‑38. Capacity Metrics Group
Metric KeyMetric NameGenerated forDescription
capacityRemainingUsingConsumers_averageCapacity
Remaining for
Average
Consumer
Prole
capacityRemainingUsingConsumers_smallCapacity
Remaining for
Small
Consumer
Prole
capacityRemainingUsingConsumers_mediumCapacity
Remaining for
Medium
Consumer
Prole
capacityRemainingUsingConsumers_largeCapacity
Remaining for
Large
Consumer
Prole
capacityRemainingCapacity
Remaining (%)
underusedpercentUnder used
(%)
ProviderNumber of average-size consumers
that can t into the capacity
remaining. An average-size consumer
demands 50% of total capacity.
ProviderNumber of small-size consumers that
can t into the capacity remaining. A
small-size consumer demands 0 - 33%
of the total capacity.
ProviderNumber of medium-size consumers
that can t into the capacity
remaining. A medium-size consumer
demands 33-66% of the total capacity.
ProviderNumber of large-size consumers that
can t into the capacity remaining. A
large-size consumer demands
66-100% of the total capacity.
BothPercent capacity remaining in the
resource container. For example, if the
resource container is memory and 2
GB out of 10 GB of memory is free,
the capacityRemaining = 20%.
BothPercent capacity not being used.
VMware, Inc. 77
vRealize Operations Definitions for Metrics, Properties, and Alerts
Table 1‑38. Capacity Metrics Group (Continued)
Metric KeyMetric NameGenerated forDescription
idletimepercentIdle time (%)BothPercent time a resource is idle based
wasteValueReclaimable
size.recommendationRecommended
optimal.vConsumption.per.pConsumptionOptimal
vConsumption.per.pConsumptionConsumption
object.demandStress Free
object.capacityUsable
object.demand.percentEective
powered.on.consumer.countNumber of
base.demandComputed
actual.capacityCurrent sizeBothActual capacity without buers
wastePercentReclaimable
Capacity
Size
consumption
ratio
ratio
Demand
Capacity
Demand (%)
powered on
consumers
Demand
Capacity (%)
on use over time. Time is a policy
seing. If not set, the default period is
30 days. For example, if a resource is
idle for a total of 6 days out of 30
days, idletimepercent = 20%.
BothAmount of reclaimable capacity
based on consumer demand over
time. Time is a policy seing. If not
set, the default period is 30 days. For
example, if a vSphere host is
congured with 10 GB of memory but
only 2 GB of memory is used on
average over 30 days, then
wasteValue = 8 GB.
BothCapacity recommendation based on
demand over time. Time is a policy
seing. If not set, the default period is
30 days. For example, if consumer
demand is 2 GB of memory on
average over 30 days, then the
capacity recommendation is 2 GB.
ProviderRatio of ideal resource consumption
to provision based on consumer
demand over time. Ideal resource
consumption is when the current
capacity satises demand. Time is a
policy seing. If not set, the default
period is 30 days.
ProviderRatio of current resource
consumption to provision based on
consumer demand.
BothDemand based on peak analysis of
raw demand values.
BothTotal capacity minus buers.
Capacity buer is a policy seing.
BothPercent capacity required by eective
demand.
BothNumber of consumers that are using
a resource.
BothDemand for an object based on self or
consumer demand without the peak
consideration policy seing.
BothPercent of reclaimable capacity based
on consumer demand over time. Time
is a policy seing. If not set, the
default period is 30 days. For
example, if a vSphere host is
congured with 10 GB of memory but
only 2 GB of memory is used on
average over 30 days, then
wastePercent = 80%.
78 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
Object-level Metrics Group
Object-level metrics are calculated to track capacity use for all objects of a particular object type.
Table 1‑39. Object-level Metrics Group
Metric KeyMetric NameDescription
summary|timeRemainingTime RemainingTime remaining before usable capacity
runs out. Usable capacity excludes
capacity reserved for HA and buers.
summary|isStressIs StressedValue equals 1 or a yellow badge
indicates that an object is stressed.
Value equals 0 or a green badge
indicates that the object is not stressed.
For a stress badge dened in a policy,
when the stress exceeds the lowest
threshold, the badge color changes
from green to yellow.
summary|capacityRemainingValueCapacity Remaining
Value
summary|oversizedIs OversizedIndicates if an object has too much
summary|idleIs IdleIndicates if an object is idle (value of 1)
summary|poweredOPowered OIndicates power state of an object.
capacity congured, value of 1, or not,
value of 0.
or not (value of 0).
Value of 1 means ON and value of 0
means OFF.
Capacity remaining based on average
consumer demand.
Capacity remaining based on small
consumer demand.
Capacity remaining based on medium
consumer demand.
Capacity remaining based on large
consumer demand.
Capacity remaining based on peak
demand or stress.
Number of capacity providers.
Number of capacity consumers.
Ratio of number of consumers to
number of providers.
Ratio of consumer to provider that
would be optimal based on consumer
demand.
VMware, Inc. 79
vRealize Operations Definitions for Metrics, Properties, and Alerts
Project-Based Metrics
Project-based metrics are calculated for a change in resources or demand that could aect capacity at some
time in the future. See vRealize Operations Manager User Guide. Most metrics appear with_whatif appended
to the capacity metric name. For example, the what-if applicable metric for capacity remaining is published
as capacityRemaining_whatif.
Badge Metrics
Badge metrics provide information for badges in the user interface. They report the health, risk, and
eciency of objects in your environment.
vRealize Operations Manager 6.x analyzes badge metric data at ve-minute averages, instead of hourly. As a
result, you might nd that eciency and risk badge calculations are more sensitive than in previous
versions. Badge metrics continue to be published nightly.
Table 1‑40. Badge Metrics
Metric KeyMetric NameDescription
badge|alert_count_criticalAlert Count CriticalCount of critical alerts on the object.
badge|alert_count_immediateAlert Count ImmediateCount of immediate alerts on the object.
badge|alert_count_infoAlert Count InfoCount of info alerts on the object.
badge| alert_count_warningAlert Count WarningCount of warning alerts on the object.
badge|anomalyAnomalyOverall score for anomalies, on a scale of 100.
badge|capacityRemainingCapacity RemainingOverall score for capacity remaining, on a scale
badge|complianceComplianceOverall score for compliance, on a scale of 100.
badge|densityDensityOverall score for density, on a scale of 100.
badge|eciencyEciencyOverall score for eciency. The score will be
badge|eciency_classicLegacy EciencyThe legacy eciency score computed on a scale
badge|eciency_stateEciency StateRepresents the state of the eciency badge with
badge|faultFaultOverall score for fault, on a scale of 100.
badge|healthHealthOverall score for health. The score will be one of
badge|health_classicLegacy HealthThe legacy health score computed on a scale of
badge|health_stateHealth StateRepresents the state of health badge with
of 100.
one of these discrete values representing each
state of the badge: Green - 100, Yellow - 75,
Orange - 50, Red - 25, Unknown: -1.
of 100 as per vCenter Operations Manager
version 5.x. For backward compatibility
purposes.
badge|stressStressOverall score of stress, on a scale of 100.
badge|timeRemainingTime Remaining - Real TimeOverall score of real time remaining, on a scale
of 100.
badge|wasteWasteOverall score of waste, on a scale of 100.
badge|workloadWorkload (%)Overall score of workload, on a scale of 100.
System Metrics
System metrics provide information used to monitor the health of the system. They help you to identify
problems in your environment.
Table 1‑41. System Metrics
Metric KeyMetric NameDescription
System Aributes|healthSelf - Health ScoreSystem health score of self resource
System Aributes|all_metricsSelf - Metric CountNumber of metrics of self resource
System Aributes|ki_metricsSelf - KPI CountNumber of KPI metrics of self resource
System Aributes|active_alarmsSelf - Active Anomaly CountNumber of active alarms of self
resource
System Aributes|new_alarmsSelf - New Anomaly CountNumber of new alarms of self resource
System Aributes|active_ki_alarmsSelf - Active KPI Breach CountNumber of active KPI alarms of self
resource
System Aributes|new_ki_alarmsSelf - New KPI Breach CountNumber of new KPI alarms of self
resource
System Aributes|total_alarmsSelf - Total AnomaliesNumber of total alarms of self resource
System Aributes|change_indexSelf - Change IndexChange index of self resource(100 -
health score)
System Aributes|child_all_metricsFull Set - Metric CountNumber of metrics of child resources
System Aributes|child_ki_metricsFull Set - KPI CountNumber of KPI metrics of child
resources
System Aributes|child_active_alarmsFull Set - Active Anomaly CountNumber of active alarms of child
resources
System Aributes|child_new_alarmsFull Set - New Anomaly CountNumber of new alarms of child
resources
System Aributes|
child_active_ki_alarms
System Aributes|
child_new_ki_alarms
Full Set - Active KPI Breach CountNumber of active KPI alarms of child
resources
Full Set - New KPI Breach CountNumber of new KPI alarms of child
resources
VMware, Inc. 81
vRealize Operations Definitions for Metrics, Properties, and Alerts
Table 1‑41. System Metrics (Continued)
Metric KeyMetric NameDescription
System Aributes|availabilityAvailabilityResource availability (0-down, 1-Up,
-1-Unknown)
System Aributes|alert_count_criticalAlert Count CriticalNumber of Critical alerts
System Aributes|
alert_count_immediate
System Aributes|
alert_count_warning
System Aributes|alert_count_infoAlert Count InfoNumber of Info alerts
Alert Count ImmediateNumber of Immediate alerts
Alert Count WarningNumber of Warning alerts
Self-Monitoring Metrics for vRealize Operations Manager
vRealize Operations Manager uses the vRealize Operations Manager adapter to collect metrics that monitor
its own performance. These self-monitoring metrics drive capacity models for vRealize Operations Manager
objects and are useful for diagnosing problems with vRealize Operations Manager.
Analytics Metrics
vRealize Operations Manager collects metrics for the vRealize Operations Manager analytics service,
including threshold checking metrics.
Table 1‑42. Analytics Metrics
Metric KeyMetric NameDescription
ActiveAlarmsActive DT SymptomsActive DT Symptoms.
ActiveAlertsActive AlertsActive alerts.
PrimaryResourcesCountNumber of primary objectsNumber of primary objects
LocalResourcesCountNumber of local objectsNumber of local objects
PrimaryMetricsCountNumber of primary metricsNumber of primary metrics
LocalMetricsCountNumber of local metricsNumber of local metrics
ReceivedResourceCountNumber of received objectsNumber of received objects
ReceivedMetricCountNumber of received metricsNumber of received metrics
LocalFDSizeNumber of forward data entriesNumber of locally stored primary
and redundant entries in forward
data region.
LocalPrimaryFDSizeNumber of primary forward data
entries
LocalFDAltSizeNumber of alternative forward data
entries
LocalPrimaryFDAltSizeNumber of alternative primary
Number of locally stored primary
entries in forward data region.
Number of locally stored primary
and redundant entries in
alternative forward data region.
Number of locally stored primary
entries in alternative forward data
region.
82 VMware, Inc.
Chapter 1 Metric Definitions in vRealize Operations Manager
Table 1‑42. Analytics Metrics (Continued)
Metric KeyMetric NameDescription
ThreadsThreadsThreads
UpStatusThreadsThreads
Overall Threshold Checking Metrics for the Analytics Service
Overall threshold checking captures various metrics for work items used to process incoming observation
data. All metrics keys for the overall threshold checking metrics begin with OverallThresholdChecking, as in
OverallThresholdChecking|Count or OverallThresholdChecking|CheckThresholdAndHealth|
OutcomeObservationsSize|TotalCount.
Table 1‑43. Overall Threshold Checking Metrics for the Analytics Service
Metric KeyMetric NameDescription
CountCountCount
Duration|TotalDurationTotalTotal length of duration (ms)
vRealize Operations Manager collects metrics for the vRealize Operations Manager cluster objects including
dynamic threshold calculation metrics and capacity computation metrics.
Metrics can be calculated for cluster objects. See “Calculated Metrics,” on page 76.
VMware, Inc. 95
vRealize Operations Definitions for Metrics, Properties, and Alerts
Cluster Metrics
Cluster metrics provide host, resource, and metric counts on the cluster.
Table 1‑76. Cluster Metrics
Metric KeyMetric NameDescription
HostCountNumber of Nodes in ClusterNumber of Nodes in Cluster
PrimaryResourcesCountNumber of primary resourcesNumber of primary resources
LocalResourcesCountNumber of local resourcesNumber of local resources
PrimaryMetricsCountNumber of primary metricsNumber of primary metrics
ReceivedResourceCountNumber of received resourcesNumber of received resources
ReceivedMetricCountNumber of received metricsNumber of received metrics
DT Metrics
DT metrics are dynamic threshold metrics for the cluster. Non-zero values appear only if metric collection
occurs while the dynamic threshold calculations are running.
CC metrics are capacity computation metrics for the cluster. Non-zero values appear only if metric collection
occurs while the capacity computation calculations are running.