jdbc_response metrics missing from robot when monitoring the local robot

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

You have configured the jdbc_response probe on one or more robots.

A monitoring profile on each robot is configured to monitor the robot itself - either using "localhost" or the hostname/IP of the same robot where jdbc_response is deployed, but the collected metrics are not found in Operator Console.

The entries in S_QOS_DATA are correct and the RN_QOS_DATA table is receiving data but the metrics do not show up under the robot(s).  The probe does not seem to be correctly associating data with the robot.

 

Environment

DX UIM - Any Version
jdbc_response probe - 1.28.0 or higher

Cause

The probe assumes all devices monitored are "remote" devices, and generates a dev_id for a remotely monitored device.

This dev_id will not correlate with the robot, so the metrics will not be properly associated with the source device.

 

Resolution

To correct this issue we have to force the probe to understand that the data belongs to the local robot.

If you use Admin Console to configure the probe, check the box "Associate Data and Alarms with Robot" at the bottom of the profile configuration window.

Set the Alarm Source Override and QoS Source Override to the name of the robot.

If you use Infrastructure Manager, this option is not available in the GUI, and must be added via Raw Configure.

1. Open the Raw Configure interface for jdbc_response (Shift+Right-click on the probe and choose Raw Configure)
2. Expand "profiles"
3. Expand the profile in question
4. Add the key "useRobotAsSource" with the value "yes"
5. set "source" and "qos_source" to the name of the robot