Missing Memory metrics with CDM MCS profiles

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

We have many robots with MCS Memory Monitor (Enhance) profiles deployed from a Group. Memory metrics are collected for all robots except for one. The robot is missing Memory data in Metrics View and SLM -> Active QoS Objects even though the profile status is Active

Spooler.log entries show 0 configs match when processing the QoS:

data  qos=QOS_MEMORY_PHYSICAL_PERC source=myrobot target=robotexample1
spooler: (Metric Plugin): M953DFFE3DE00A17334944FBB0AE170C9 (cdm) matched (0 configs)

Resolution

This issue is seen when there is a mismatch of the qos_target parameter defined in the plugin_metric.cfg and target processed by the spooler probe.

Example: 

Spooler.log 

data  qos=QOS_MEMORY_PHYSICAL_PERC source=robotexample1 target=robotexample2

plugin_metric.cfg 

<QOS_MEMORY_PHYSICAL_PERC>

publish_baseline = false
qos_label = Physical Memory Usage (%)
 subsys = 1.1.1.2
qos_name = QOS_MEMORY_PHYSICAL_PERC
qos_source = ~.*
qos_target = robotexample1
publish_qos = true
alarm = false

</QOS_MEMORY_PHYSICAL_PERC

To resolve this issue, enable the 'Allow QoS Source as Target' option in the Setup cdm (Enhanced) profile at the device level and save the change.

Example:

Additional Information

If no resolution from the above steps,

1. Refresh plugin_metrig.cfg - remotely log in to the end robot(s) with the issue, backup, and delete the existing plugin_metric.cfg file (path: ..\Nimsoft\plugins\plugin_metric)

2. (Re-)deploy the latest supported robot_update version on the end robot(s) with the issue.