Robots that report to a secondary hub are not generating alerts per MCS/Alarm Policy settings

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Deployed MCS profiles and Alarm policies for robots that report to a secondary hub and all robots do not generate any alarms. Note that MSC profiles for robots under the UIM Server/Primary hub work fine.

1.  Checked the plugin_metric.cfg on the robots and noticed that policy entries were missing

2. The following message is captured on the robot's spooler.log

spooler: policy_profile_pull_thread  - pull_monitoring_configuration to .../configuration_reader_service failed with communication error

 

Environment

Hub and Robots with version 23.4+

Cause

Communication issues with the configuration_reader_service on secondary hub

Resolution

1.  Check if configuration_reader_service probe is installed on the secondary hub

2.  Deploy the configuration_reader_service if it is missing

Additional Information

Configuration Reader Service (CRS) Release Notes