discovery_server does not merge metrics collected with rsp to the device name when device registered by api

book

Article ID: 144431

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

The rsp probe is monitoring devices using the ip address but the discovery_server does not merge those metrics to the device name and creates a new device using the ip address.

All of the rsp profiles were created in a USM group of devices using their names, but rsp is configured to use the ip address and new devices are created, so the USM group of device names has no metrics. 

We created remote devices using the rest api so we had the devices in USM to create a group and apply the rsp monitoring via MCS.

Example:

curl -v -u administrator:{password} -X POST -H "Content-Type: application/xml" -d "<device><name>Windows2003</name><label>Windows2003</label><alias>Windows2003</alias><description>Windows 2003</description><os_type>Windows</os_type><nimbus_type>0</nimbus_type><type>E</type><primaryOrigin>origin</primaryOrigin><ipAddresses>xxx.xxx.xxx.xxx</ipAddresses></device>" http://{Host running uimapi}:{port if not 80}/uimapi/devices

Environment

Release : 9.2.0

Component : UIM - DISCOVERY_SERVER

Resolution

When the devices were created with rest api they were created with a specific origin.

When rsp registered the device it has a different origin

The default correlation rules were therefore not able to correlate to the rsp collected metrics as there is no rule that could correlate base solely on IP where the origin is different

Solution was to use the treat_as_equal_values section added to the defined correlation property

  •             <treat_as_equal_values>
  •                <PostNL>
  •                   origin1 = RSP Test
  •                   origin2 = Agentless
  •                </PostNL>
  •                 <Agentless>
  •                   origin1 = Agentless
  •                   origin2 = Tooling and automation team
  •                </Agentless>
  •             </treat_as_equal_values>


This allows the <ip_origin> correlation rule to correctly correlate the devices

The treat_as_equal_values is documented in the section "Origin Handling Using treat_as_equal_values" in the following page Device Correlation Configuration