vSphere Data Center
he use case for higher level objects, such as Data center, Custom DC, vCenter and World need to reflect the nature of the object. The complex nature of the object needs to be accounted for. For example, a vCenter Data center object may span across physical data centers. This comes from the limitation that a stretched cluster is not a child of 2 separate data center objects, even when the clusters are physically in 2 separate buildings.
Large objects such as vCenter also tend to host clusters that serves different purpose, and hence are not compatible with one another. A free capacity on the NSX Edge cluster may not mean the business VM can be deployed, due to different storage, security, and network requirements.
These also apply to vRealize Custom Data Center, vCenter and World objects.
|Utilization (KB)||Memory utilization level based on descendant VMs utilization. Includes reservations, limits and overhead to run VMs||Sum ([HostSystem]Memory|Utilization)|
|Total Capacity (KB)||Amount of physical memory configured on descendant ESXi hosts||Sum ([HostSystem]Memory|Total Capacity)|
|Usable Capacity (KB)||Amount of usable memory resources for VMs after considering reservations for vSphere High Availability (HA) and other vSphere Services.||Sum ([Cluster]Memory|Usable Capacity)|
|Workload (%)||[(Memory|Machine Demand + Memory|ESX System usage) / Memory|Usable Capacity] * 100|
|Utilization (GB)||Storage space utilized on connected vSphere Datastores||Sum ([Datastore]Disk Space|Utilization)|
|Total Capacity (GB)||Total Storage space available on connected vSphere Datastores||Sum ([Datastore]Disk Space|Total Capacity)|
|Workload (%)||[(Disk Space|Utilization)/(Disk Space|Total Capacity)] * 100|
|Demand (MHz)||CPU utilization level based on descendant VMs utilization. Includes reservations, limits and overhead to run VMs||Sum ([HostSystem]CPU|Demand)|
|Total Capacity (MHz)||Amount of CPU resources configured on descendant ESXi hosts||Sum ([HostSystem]CPU|Total Capacity)|
|Usable Capacity (MHz)||Amount of usable CPU resources for VMs after considering reservations for vSphere High Availability (HA) and other vSphere Services.||Sum ([Cluster]CPU|Usable Capacity)|
|Overhead (MHz)||Sum ([HostSystem]CPU|Overhead)|
|Demand without overhead (MHz)||Sum ([HostSystem]CPU|Demand without Overhead)|
|Workload (%)||[(CPU|Demand without overhead + CPU|Overhead) / CPU|Usable Capacity] * 100|
|Maximum number of VMs|
The supported configuration maximum as stated in vSphere Configuration website. This number tends to be very high relative to typical deployment.
The metrics exist for vSphere, vCenter Data Center, vSphere Cluster, ESXi Host, Datastore and vRealize Operations Custom Data Center object
|Number of Hosts * Maximum number of VMs per ESXi Host|
Metric and Property Changes
One popular request among customers is we simplify our metrics and properties to improve both scalability and usability. You notice that some metrics are marked for deprecation:
- vRealize Operations 8.3
- vRealize Operations 8.2
- We disable some instanced metrics here. You can enable them back.
- vRealize Operations 8.1
- vRealize Operations 8.0
- vRealize Operations 7.5
- vRealize Operations 7.0
Metrics and Properties can be deprecated or disabled for the following reasons:
- They are rarely used and hence have been disabled. If you plan to use them, you can enable them.
- They are duplicates. The replacement metric are provided.
- They are not the right indicator of performance or capacity issues. We have provided replacement metrics and guidance on how you should interpret the results.
More details here.
This page was last updated on June 30, 2021 by Stellios Williams with commit message: "Cleaned MD syntax"