Performance Data not shown for some servers after deploying Profiles with MCS on DX UIM 23.4
Article ID: 390457
Updated On:
Products
Issue/Introduction
We configured monitoring using MCS but we are not able to view performance / QOS / Metrics data of some devices / robots in OC Metric viewer and on OC Default metrics / Golden Metrics.
For some servers we are seeing metrics but for some others not.
We have verified that everything is working with QOS in general, queues between hubs, data_engine inserting data correctly and devices are discovered correctly, and also verified that have configured the Configure the ROBOT_NIS_CACHE Subject queue in DX UIM 23.4
Environment
DX UIM 23.4.*
Cause
The issue can be caused by using Legacy (non-Enhanced) Monitoring Configuration Services (MCS) Templates and profiles in DX UIM 23.4 and later. DX UIM 23.4 and later do not support Legacy MCS profiles.
When using MCS in 23.4.3, the plugin_metric.cfg in each target robot (located in nimsoft/plugins) is a configuration file that filters out the metrics sent by robot to the bus/hub.
The plugin_metric.cfg only supports MCS Enhanced Profiles. Deploying Legacy MCS Profiles will not translate / send the configuration to the plugin_metric.cfg, therefore NO data will be sent from those robots where the legacy profiles are deployed. Additionally, no default or custom Alarm Policies can be created when using Legacy Profiles.
Resolution
If you have deployed some Legacy (non-Enhanced) Monitoring Configuration Services (MCS) such as "CPU monitor", or Default Disks(s), or Port Check, delete these profiles and then create new Enhanced MCS profiles.
Legacy (non-Enhanced) profiles are not supported in DX UIM 23.4.
Highlighted in Yellow in the example below are the Enhanced Templates. Only the Templates named with the (Enhanced) tag should be deployed.
Ignore the legacy templates which will deploy unsupported MCS profiles:
Additional Information
Feedback
