CDM on VM as cause of duplicate metrics

[vrbto01]

Hello,

how to avoid duplicate metrics data from vmware and cmd probes?

 

For example following docs says about CPU:

 

vmware probe collects

VM_CPU

CPU Used (% of available)

Percent

Total CPU usage

v1.0

capman_da probe collects this vmware metrics I suppose as:

GBL_LS_VIRT_CPU_UTIL Logical System virtual CPU Utilization percent vm_cpu_usage_perc

 

cdm probe collects

Total CPU Usage

The percentage of time for which all CPUs of the system were used.

4.7

capman_da probe collects cdm metrics:

GBL_CPU_UTIL CPU Utilization percent cpu_usage

 

Isn't that same?

 

USM shows machines detected by robot/cdm and by vmware probe somehow merged together displaying all relevant data as on one machine. It's correct but how to avoid duplicate monitoring?

 

The cdm metrics description section at CapMan documentation is with header "Metrics Collected for Physical Systems" also mentions this data source as "CA UIM Physical data source" but in our environment virtual machines are monitored by CDM probe. It's a solution design.

 

Thank you

[Kip_Lamb]

Hey,

When you have a situation like described, a server that is getting both physical and virtual metrics, you will have issues with the server's reported configuration. The server will be reported as physical or virtual depending on which data source migrated last. So, in this situation, would not explain 'duplicate metrics', as one is reporting GBL_LS_VIRT_CPU_UTIL, LS means 'Logical Server' or another name for a VM, it is a unique metric that is reporting CPU utilization relative to the VM. So while this is a different metric than the GBL_CPU_UTIL, the values would be similar/same, but NOT stored as the same metric.

In the situation described, you would have entity duplication, meaning you would have a virtual entity and a physical entity.

To avoid metric duplication, ideally the VM's would not be included in the data pull from the CDM probe. This can be accomplished by careful selection of systems in the CDM probe.

[Anon Anon]

Can't this problem be solved using exclude groupings?   This is how it was solved here with 3 different input datasources.  My only problem has been when I had a server originally in one datasource then start being loaded in another higher priority datasource.

[Legacy User]

Chris,

  Yes the Exclude solution you have might work to solve this problem.  This solution is not part of the product, it is a services developed and delivered solution.

 

David