Metrics not updated in database. We can see data in DrNimbus, but nothing in s_qos_definition on s_qos_data
In the secondary hub only QOS_MESSAGE was pushed to the primary hub, and not QOS_DEFINITION. So, qos from probes that were not reported by any of robots that are on the primary hub were getting dropped as there was no qos_definition associated with it. sqlserver and oracle server were two such cases. None of the primary hub robots had sqlserver or oracle instances. In contrast, cdm probe for example was deployed to one of the robots under the primary hub, hence did not face this issue.
Release : 20.3
Component : UIM - DATA_ENGINE