Vmware probe monitoring
search cancel

Vmware probe monitoring

book

Article ID: 206888

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We have configured VMware probe monitoring for few VCenters in different HUBs.

However, hostname on both alerts are very different. Both alerts are configured on different hubs. We need it to be in similar format.

 

 

 

Environment

Release : 20.1

Component : UNIFIED INFRASTRUCTURE MGMT

Resolution

Looking at both working & non-working, the problem is with this property "multi_tenant_path = both"
This has been set to None in working probe "multi_tenant_path = none"
 
target
For VMs and their children a QoS target component is augmented to list the full path from the containing Data Center down to the VM. If this component resides within a template and pool those will be included in the path.
 
source
For VMs and their children a QoS source component is augmented to list the full path from the containing Data Center down to the VM. If this component resides within a template and pool those will be included in the path.
 
both
This option enables both the target and source settings listed above.
The following examples illustrate the path that would display in your reports:

Target Example: 
If you enabled the Memory metric on a VM:
Without this setting the target would simply be Memory.
With this setting the target would be of the form
<DataCenter Name>/<Cluster Name[/<Optional Template Name>[/<Optional pool name>]] ::<VM Name>::MemoryDataCenter-1/Cluster-1/desktopTemplate/desktops::VM-1::Memory Source Example:
 
If you enabled the Memory metric on a VM:
Without this setting the source would simply be the VMs name.
With this setting the source would be of the form
<DataCenter Name>/<Cluster Name[/<Optional Template Name>[/<Optional pool name>]] ::<VM Name>DataCenter-1/Cluster-1/desktopTemplate/desktops::VM-1
 
So, you may have to disable this option in the probe in question