url_response 5.01 via MCS creates duplicate device as doesn't merge into master device

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Differently from previous versions of url_response, this version 5.01 when a URL Check (Enhanced) is pushed via MCS, creates a duplicate device as it doesn't merge the discovered device with the robot that is hosting that device. 

Specifically, when trying to monitor the OC URL, url_response 4.56 and earlier, when pushing a URL Check (Enhanced) to the robot for monitoring the OC, the OC discovered and its metrics would appear under the OC robot, merged devices. 

 since 5.01 this is no longer happening as a second device is create. 

How can I fix this? 

Environment

• DX UIM 23.4.*
• url_response 5.01

Cause

url_response 5.01 introduced improved association of metrics and alarms for data to be sent to DX O2

 

When used via MCS, url_response 5.01 via  generates a discovery additional attribute "correlation names" into the CM_DEVICE_ATTRIBUTE  and this behavior is what is different from what url_response 4.56 and earlier. When the "Correlation Names" attribute added into cm_device_attribute does NOT match the "Correlation Names" already present of the robot, the discovery_server applies the "unmatch" rule as per default discovery configuration, and creates a new master device (separate cs_id) which appear as a "duplicate" in OC.  

Resolution

The attached url_response build  url_response-5.01-T1-20251022.zip adjusts this behavior so that in this particular scenario, no duplication is created. 

This fix will be included in the next GA Version of the probe.