Qos Monitor update failed messages in qos_processor log in UIM 20.4

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• DX Unified Infrastructure Management (Nimsoft / UIM)
• Unified Infrastructure Management for Mainframe
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

I have reinstalled a robot but since I did that, I have this errors in the qos_processor log.

Feb 11 15:59:37:844 [Qos Monitor Database Updater #1, qos_processor] Monitor update failed for '5301303A3AC8764218BF2F687056F5D05B11A1A3-exxxxxx632:   Feb 11 15:59:37:844 [Qos Monitor Database Updater #1, qos_processor] Monitor update failed for '2B19CA69E6F02498A1A4731FE7BD2EB19C8C7CC3-exxxxxx632:   Feb 11 15:59:37:844 [Qos Monitor Database Updater #1, qos_processor] Monitor update failed for '1999D67A5C7CBBD373FCD389A0B946BA8A3E2D69-eixxxxxx2:   Feb 11 15:59:37:844 [Qos Monitor Database Updater #1, qos_processor] Monitor update failed for 'FF8F234545F1ADFD711EE64562D533B648B0023B-exxxxxx632:

There's no new data from this server, how can I delete all of this qos data immediately so it will be recreated?

Environment

Release : 20.4

Component : UIM - QOS_PRROCESSOR

Resolution

To delete all qos /data from a specific server as desired/described, 

 

- Stop server robot

- Delete qos/data

- Start robot and let it register/recreate all data again,

You can delete the robot via the Operator Console Inventory.

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-4/installing/discover-systems-to-monitor/advanced-configuration/remove-devices-in-usm.html

But the QOS data won't 'age out' until the retention period ends, e.g., 35 days as per whatever the data_engine setting is set to for raw data.

You can also then remove the robot from the Robots tab in the Hub GUI.

If you want to remove all of the QOS data immediately you can follow this community post from Luc Christiaens to delete the QOS via the command line.

https://community.broadcom.com/enterprisesoftware/communities/community-home/digestviewer/viewthread?MessageKey=27b4d9b2-5d9e-48a3-8e56-07e57f85fced&CommunityKey=170eb4e5-a593-4af2-ad1d-f7655e31513b&tab=digestviewer

Also, suggest running through this process to get rid of the dev_id completely.

Remove master devices by cs_key
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-4/installing/discover-systems-to-monitor/advanced-configuration/remove-master-devices-through-discovery-server.html