How to update origin for robot inactive alarm

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

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.

 

Capture_controller.PNG

 

 Capture_origin1.PNG

Instructions:

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

1.open 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

<enrichment-source>
  <cmdbs>
     <origin_update>
        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>
    </origin_update>
 </cmdbs>
</enrichment-source>

Capture_enrichment-rules01.PNG

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

5.create keys and values as below

<enrichment-rules>
  exclusive_enrichment = no

   <1>
     match_alarm_field = udata.subsys
     match_alarm_regexp = 1.2.2
     use_enricher = origin_update
    lookup_by_alarm_field = robot
    lookup_by_regexp =
      <overwrite-rules>
       origin = [cmdb.origin]
    </overwrite-rules>
 </1>

</enrichment-rules>

Capture_enrichment-rules02.PNG

Capture_enrichment-rules2.PNG

6.save and restart NAS probe

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

 Capture_origin2.PNG

Additional Information:

Oracle DB example:
connection_url = jdbc:oracle:thin:@//172.17.4.12:1521/ORCL

mysql DB example:
connection_url = jdbc:mysql://172.17.0.12:3306/choslm

 

You can see more examples from the URL below.

https://docops.ca.com/ca-unified-infrastructure-management-probes/ga/en/alphabetical-probe-articles/nas-alarm-server/alarm_enrichment-raw-configuration#alarm_enrichmentRawConfiguration-SettingupcmdbsEnvironment