How to update origin for robot inactive alarm

Document ID : KB000010605
Last Modified Date : 14/02/2018
Show Technical Document Details

When robot inactive situation happens, the robot inactive alarm is generated by hub (not robot controller) so the alarm comes in with the origin of hub instead of the origin of robot configured in controller probe.  This makes some issues with filtering alarms based on origin.






The following workaround will update the alarm with the robot origin configured in CM_COMPUTER_SYSTEM table. NAS Raw Configure..

2.create new section 'origin_update' under cmdbs section

3.create keys and values as below under the 'origin_update' section
NOTE: replace <sqlserver_ip_address>, <db_user> and <password> with appropriate values

        active = yes
        connection_url = jdbc:sqlserver://<sqlserver_ip_address>:1433;DatabaseName=CA_UIM;
        query = SELECT robot, origin FROM CM_NIMBUS_ROBOT where robot=?
        population_query = SELECT robot, origin FROM CM_NIMBUS_ROBOT
        user = <db_user>
       password = <password>


4.create new section # under enrichment-rules section and create overwrite-rules section under the # section

5.create keys and values as below

  exclusive_enrichment = no

     match_alarm_field = udata.subsys
     match_alarm_regexp = 1.2.2
     use_enricher = origin_update
    lookup_by_alarm_field = robot
    lookup_by_regexp =
       origin = [cmdb.origin]



Capture_enrichment-rules2.PNG and restart NAS probe

7.check if the origin is updated for robot inactive alarm


Additional Information:

Oracle DB example:
connection_url = jdbc:oracle:thin:@//

mysql DB example:
connection_url = jdbc:mysql://


You can see more examples from the URL below.