Lookup information and metrics for VMware ETLs
This topic lists Configuration and Performance metrics in BMC Helix Continuous Optimization collected by VMware ETL modules for entities such as Virtual Hosts, Clusters, VMs, Resource Pools, Datastores, Datastore Clusters, and data centers.
Lookup information
Entity | Entity type | Lookup fields | |
---|---|---|---|
Strong | Weak | ||
Datacenter | dc | PARENT_VCUUID&&VMW_VMREF or PARENT_VCNAME&&VMW_VMREF | Not applicable |
Virtual Cluster - VMware | vhc:vmw | PARENT_VCUUID&&VMW_VMREF or PARENT_VCNAME&&VMW_VMREF |
|
Datastore | ds |
| DATASTORE_NAME (If the datastore name does not start with "local") |
Virtual Host - VMware | vh:vmw |
| HOSTNAME&&NAME |
Virtual Machine - VMware | gm:vmw | PARENT_VCUUID&&VMW_VMREF or PARENT_VCNAME&&VMW_VMREF |
|
Virtual Application - VMware vApp | gapp:vapp |
|
|
Resource Pool | rp | PARENT_VCUUID&&VMW_VMREF or PARENT_VCNAME&&VMW_VMREF |
|
Datastore Cluster - VMware | dsc:vmw | PARENT_VCUUID&&VMW_VMREF or PARENT_VCNAME&&VMW_VMREF | PARENT_VCNAME&&DATASTORE_CLUSTER_NAME |
Entity relationship
The Workspace navigation tree shows all the visible relationships that are currently valid. The available relationship types are CONTAINS and USES. The CONTAINS relationship type applies to Parent entities whereas the USES relationship type applies to child entities. For more details, see Relationships.
The following table lists various parent and child combinations of entities managed by this ETL along with a brief description of such combinations. The last column denotes whether the Workspace entity tree displays the corresponding parent-child entity relationship.
Primary (Parent) entity | Secondary (child) entity | Description | Display status |
---|---|---|---|
Datastore | Virtual Machine - VMware | Datastore contains VM | Hidden |
Datacenter | Datastore Cluster - VMware | Datacenter contains Datastore Cluster | Visible |
Datacenter | Virtual Cluster - VMware | Datacenter contains Virtual Cluster | Visible |
Datacenter | Virtual Host - VMware | Datacenter contains Virtual Host | Visible |
Datastore Cluster - VMware | Datastore | Datastore Cluster contains Datastore | Visible |
Resource Pool | Virtual Application - VMware vApp | Resource Pool contains VMware vApp | Visible |
Resource Pool | Resource Pool | Resource Pool contains Resource Pool | Visible |
Resource Pool | Virtual Machine - VMware | Resource Pool contains VM | Visible |
Virtual Cluster - VMware | Virtual Host - VMware | Virtual Cluster contains Virtual Host | Visible |
Virtual Cluster - VMware | Virtual Application - VMware vApp | Virtual Cluster contains VMware vApp | Visible |
Virtual Cluster - VMware | Resource Pool | Virtual Cluster contains Resource Pool | Visible |
Virtual Cluster - VMware | Virtual Machine - VMware | Virtual Cluster contains VM | Visible |
Virtual Cluster - VMware | Datastore Cluster - VMware | Virtual Cluster uses Datastore Cluster | Hidden |
Virtual Cluster - VMware | Datastore | Virtual Cluster uses Datastore | Visible |
Virtual Host - VMware | Virtual Application - VMware vApp | Virtual Host contains VMware vApp | Visible |
Virtual Host - VMware | Resource Pool | Virtual Host contains Resource Pool | Visible |
Virtual Host - VMware | Virtual Machine - VMware | Virtual Host contains VM | Hidden |
Virtual Host - VMware | Datastore Cluster - VMware | Virtual Host uses Datastore Cluster | Hidden |
Virtual Host - VMware | Datastore | Virtual Host uses Datastore | Hidden |
Virtual Host configuration metrics
BMC Helix Continuous Optimization metric | Description | Available in Extractor Service | Available in History Extractor |
---|---|---|---|
BYDISK_MODEL | The model of the disk. | Yes | Yes |
BYDISK_SIZE | The disk size in bytes. | Yes | Yes |
BYDSTORE_ID | The id of the datastore. The subobject specifies the Datastore id. | Yes | Yes |
BYDSTORE_NAME | The Name of the datastore. The subobject specifies the Datastore id. | Yes | Yes |
BYDSTORE_SIZE | The total size of the datastore in bytes. The subobject specifies the Datastore id. | Yes | Yes |
BYDSTORE_TYPE | The Type of the datastore. The subobject specifies the Datastore id. | Yes | Yes |
BYDSTORE_URL | The URL of the datastore. The subobject specifies the Datastore id. | Yes | Yes |
BYIF_BANDWIDTH | The bandwidth of the network interface. | Yes | Yes |
BYLDISK_EXTENTS_NAMES | The name of the partitions used to extent a VMFS filesystem, for each VMFS filesystem of the system. | Yes | Yes |
BYLDISK_SIZE | The logical disk size in bytes. | Yes | Yes |
CLUSTER_NAME | The name of the cluster to which this server belongs. | Yes | Yes |
CPU_CORES_PER_SOCKET | The CPU cores per socket. | Yes | Yes |
CPU_FAMILY | The architecture type of CPU. | Yes | No |
CPU_MHZ | The frequency of each physical CPU core | Yes | Yes |
CPU_MODEL | The hardware model of CPU. | Yes | Yes |
CPU_NUM | The number of CPU cores physically on the system | Yes | Yes |
CPU_PACKAGE_NUM | The number of CPU packages physically installed on the system sockets. | Yes | Yes |
CPU_THREADS_PER_CORE | The CPU threads per core. | Yes | No |
CPU_TOTAL_MHZ | The total frequency of CPU (the sum of each physical CPU core) | Yes | Yes |
DISK_NUM | The number of disks on the system. | Yes | No |
HOST_ID | The hardware identifier of the host. For VMWare hosts, it is the UUID. | Yes | No |
HOST_CONNECTION_STATE | Virtual Host Connection State (connected|disconnected|notResponding) | Yes | |
HW_MODEL | The hardware model of the system. | Yes | Yes |
HW_VENDOR1 | The hardware vendor of the system. | Yes | No |
BYHBA_STATUS2,3 | The status of the host adapter. | No | Yes |
BYHBA_BANDWIDTH_CURRENT2,3 | The speed of HBA adapter in bit/s. | No | Yes |
BYHBA_BANDWIDTH2 | Maximum speed of the host adapter in bit/s. | No | Yes |
BYHBA_MODEL3 | Model of the HostFibreChannel host bus adapter. | No | Yes |
LCPU_NUM | The total number of Logical CPUs on the system. | Yes | No |
LDISK_NUM | The number of logical disks in the system. | Yes | Yes |
MAINTENANCE_MODE | The value indicates whether the system is in maintenance mode. Value is 1 if the system is in maintenance mode, 0 otherwise. | Yes | Yes |
NETIF_NUM | The number of network interfaces on the system. | Yes | Yes |
NET_BANDWIDTH | The network bandwidth. | Yes | Yes |
NET_IP_ADDRESS | The main IP address of the system. | Yes | No |
OS_FAMILY | A string representing the family of the operating system. | Yes | No |
OS_TYPE | A string representing the name of the operating system. | Yes | Yes |
OS_VER | A string representing the version of the operating system. | Yes | Yes |
TIMEZONE | A string representing the timezone international code for the system | Yes | Yes |
TOTAL_DSTORE_SIZE | The sum of the size of the datastores used by this system in bytes. | Yes | Yes |
TOTAL_REAL_MEM | The total amount of memory installed on the system. | Yes | Yes |
VIRTUALCENTER_NAME | The name of the Virtual Center. | Yes | Yes |
PWR_MAX | The maximum KW capacity. | Yes | No |
1 Indicates metrics that are set at level 4. These metrics are imported only when the collection level of the ETL is set to ‘Extended’.
For information about changing the collection level, see VMware vCenter Extractor Service. Alternatively, you can create a custom metric profile to change the level of these metrics. For details, see Adding and managing metric profiles.
2 Indicates metrics available for HostInternetScsiHba Host Bus Adapter if the HBA card is configured.
3 Indicates metrics available for HostFibreChannelHba Host Bus Adapter if the HBA card is configured.
Virtual Host performance metrics
1 Indicates metrics that are set at level 4. These metrics are imported only when the collection level of the ETL is set to ‘Extended’. For information about changing the collection level, see VMware-vCenter-Extractor-Service. Alternatively, you can create a custom metric profile to change the level of these metrics. For more information, see Adding-and-managing-metric-profiles.
2 Indicates metrics for which custom details can be imported using the VMware - vCenter Extractor Service ETL.
Virtual Host Datastore performance metrics
All the metrics are set at level 4. These metrics are imported only when the collection level of the ETL is set to ‘Extended’. For information about changing the collection level, see VMware-vCenter-Extractor-Service. Alternatively, you can create a custom metric profile to change the level of these metrics. For details, see Adding-and-managing-metric-profiles.
Virtual Machine configuration metrics
1 Indicates metrics that are set at level 4. These metrics are imported only when the collection level of the ETL is set to ‘Extended’. For information about changing the collection level, see VMware-vCenter-Extractor-Service. Alternatively, you can create a custom metric profile to change the level of these metrics. For more information, see Adding-and-managing-metric-profiles.
Virtual Machine performance metrics
1 Indicates metrics that are set at level 4. These metrics are imported only when the collection level of the ETL is set to ‘Extended’. For information about changing the collection level, see VMware-vCenter-Extractor-Service. Alternatively, you can create a custom metric profile to change the level of these metrics. For more information, see Adding-and-managing-metric-profiles.
2 Indicates metrics for which details will be imported every 15 minutes irrespective of the resolution used in the VMware - vCenter Extractor Service ETL.
3 Indicates metrics for which custom details can be imported using the VMware - vCenter Extractor Service ETL.
Virtual Machine Datastore performance metrics
All the metrics are set at level 4. These metrics are imported only when the collection level of the ETL is set to ‘Extended’. For information about changing the collection level, see VMware-vCenter-Extractor-Service. Alternatively, you can create a custom metric profile to change the level of these metrics. For details, see Adding-and-managing-metric-profiles.
Virtual Cluster configuration metrics
1 Metrics are available only for clusters that have shared datastores in them.
Virtual Cluster performance metrics
1 Indicates metrics for which custom details can be imported using the VMware - vCenter Extractor Service ETL.
2 Metrics are available only for clusters that have shared datastores in them.
Back to top ↑
Virtual Cluster Datastore performance metrics
All the metrics are set at level 3. These metrics are imported only when the collection level of the ETL is set to ‘Standard’. For information about changing the collection level, see VMware-vCenter-Extractor-Service.
Resource Pool configuration metrics
Resource Pool performance metrics
1 Indicates metrics for which custom details can be imported using the VMware - vCenter Extractor Service ETL.
Datastore configuration metrics
1 Indicates metrics that are set at level 4. These metrics are imported only when the collection level of the ETL is set to ‘Extended’. For information about changing the collection level, see VMware-vCenter-Extractor-Service. Alternatively, you can create a custom metric profile to change the level of these metrics. For more information, see Adding-and-managing-metric-profiles.
2 The metric is not available for a vSAN datastore.
Datastore performance metrics
1 Indicates metrics that are set at level 4. These metrics are imported only when the collection level of the ETL is set to ‘Extended’. For information about changing the collection level, see VMware-vCenter-Extractor-Service. Alternatively, you can create a custom metric profile to change the level of these metrics. For more information, see Adding-and-managing-metric-profiles.
2 Indicates metrics that are set at level 3. These metrics are imported only when the collection level of the ETL is set to ‘Standard’.
Data center configuration metrics
Data center performance metrics
Datastore cluster configuration metrics
Datastore cluster performance metrics