AnsweredAssumed Answered

alarm enrichment of user_tag_1 and user_tag_2 failing

Question asked by 1_hdoan on Feb 7, 2014
Latest reply on Feb 13, 2014 by 1_hdoan

We recently upgraded to NMS 6.5 and discovered that the alarm enrichment probe got incorporated into the nas.

 

So reconfigured the nas to enrich.  We can get custom_1 through custom_5 to enrich with new data from our enrichment database.  However, no matter what we do, user_tag_1 and 2 will not enrich with anything.

 

Here is the nas config:

 

<enrichment-source>
<cmdbs>
<alarm_enrichment>
   active = true
   connection_url = jdbc:sqlserver://<some_server>:<Port_number>;DatabaseName=NimsoftSLM
   user = nimsoft_install
   password = <Encryptd password>
   query = select hostname as id, hostname, kbid, rto, application from MGI_Alarm_Enrichment where hostname = ?
   population_query = select hostname as id, hostname, kbid, rto, application from MGI_Alarm_Enrichment
</alarm_enrichment>

.

.

.

<enrichment-rules>
   exclusive_enrichment = no
<1>
   match_alarm_field = prid
   match_alarm_regexp = (url_response|dns_response)
   use_enricher = alarm_enrichment
   lookup_by_alarm_field = udata.source
   lookup_by_regexp =
      <overwrite-rules>
         udata.user_tag_1 = [cmdb.hostname]
         udata.user_tag_2 = [cmdb.rto]
         udata.custom_2 = [cmdb.hostname]
         udata.custom_3 = [cmdb.application]
         udata.custom_5 = [cmdb.kbid]
     </overwrite-rules>
</1>

 

 

I have tried changing the overwrite rules to use just user_tag_1, user_tag1, and udata.user_tag1 w/o success.

Support doesn't seem to know what is happening either.

 

The old alarm enrichment probe that we got from proffessional services worked perfectly if we used user_tag_1 and user_tag_2 in the overwritew rules.  Not sure what is going on with the new enrichment probe.

Outcomes