The qos_processor probe will ordinarily automatically detect Origin changes on robots/hubs in the environment and update S_QOS_DATA with the new Origin. It can also be configured to enrich Origins via a Ruby script.
Sometimes this will be seen to fail, and the original Origin remains in place. Errors such as the following will be seen in the qos_processor.log on level 3 or higher:
Dec 10 17:18:19:569 [Qos Monitor Database Updater #1, qos_processor] Did not update qos withupdate s_qos_data set origin = ‘NEWORIGIN’, host = ‘hostname’, robot = 'robotname', probe = 'probename', nim_origin = ‘MYORIGIN’, modifier = 'nimsoft', samplerate = 3600 where checksum = '3AA8DD709B5B60D9E2532AB3946B7C49285AADD0'
This is caused by a defect in qos_processor 1.24 or lower. In most cases it is a result of QoS from custom probes which do not have “QOS_” prepended to the names of QoS messages they are sending.
Upgrading to UIM 8.31 or later will automatically upgrade the qos_processor probe to version 1.25 or higher.
If you are unable to upgrade your UIM installation at this time, please contact CA Support who will provide a hotfix.
Release: CNMSPP99000-8.2-Unified Infrastructure Mgmt-Server Pack-- On Prem