cdm MCS QoS not collected due to plugin_metric.cfg failure

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We are facing a problem where no cdm QoS metrics are being collected across our robots. Looking into the issue, we found that the plugin_metric.cfg files do not contain the CPU, Memory, and Disk profiles anymore. These profiles derive from group profiles, but the file now only contains "$setup_profile$ = 1" entries for each profile ID. 

Environment

• DX UIM 23.4 CU7
• Robots: 23.4 CU7
• cdm probe: 8.06
• Configuration Reader Service: 23.4 CU7
• OS: Windows

Cause

The Monitoring Configuration Service (MCS) might be failing to properly deploy or synchronize the full metric configuration to the local robot cache, leaving the configuration files in an incomplete state that prevents data collection. 

Resolution

 The following steps outline the diagnostic and resolution process to restore QoS collection:

• Verify Infrastructure Health: Ensure that the required management queues are present on the hubs.

1. 1. Check for the existence of the robot_niscache and probe_discovery queues.
   2. If these are missing, create them and then re-push the MCS profiles.

Perform nis_cache Reset To verify if local cache corruption is the cause on a specific robot:

1. 1. Open the controller probe GUI on the affected robot.
   2. Access the callbacks using CTRL+P and enable expert mode.
   3. Execute the nis_cache_clean callback.
   4. Execute the _reset_device_id_and_restart callback.
   5. Observe if the plugin_metric.cfg is repopulated correctly after the robot restarts and syncs with MCS.

 

• Full Probe Reinstallation: If redeploying profiles does not fix the inconsistency, a manual removal and fresh deployment of the cdm probe is required:

  1. Ensure you have CDM on the latest version in the archive (Eg. 8.08)
  2. Ensure you have the latest CDM template 8.08 deployed and migrated/Activated correctly)
  3. Delete the cdm probe from the affected robot using Infrastructure Manager or Admin Console.
  4. Redeploy the probe by either waiting for MCS to auto-deploy or by making a small change to the MCS cdm setup profile to force a push.
  5. Ensure the latest available version (e.g., cdm 8.08) is installed.
  6. Verify that the plugin_metric.cfg now contains the correct profiles and that metrics are visible in the Operator Console Metric View.

Additional Information

cdm MCS Profile Type Configuration