Problem with unique identifier & Script monitor using ta

Problem with unique identifier & Script monitor using ta

The problem I am having is when using an output file containing tables generated from MQSeries events. Unfortunately there are no unique column identifiers in the output table. See example below,

<--table perfevents starts-->
Timestamp,EventType,EventDescription,EventVal,QueueManager,QueueName,QueueDepth
2007031223353024,MQCMD_PERFM_EVENT,MQRC_Q_DEPTH_HIGH,2224,HOME_MGR,EVENT_TESTING,5
2007031223353043,MQCMD_PERFM_EVENT,MQRC_Q_SERVICE_INTERVAL_HIGH,2226,HOME_MGR,EVENT_TESTING,5
2007031223353116,MQCMD_PERFM_EVENT,MQRC_Q_FULL,2053,HOME_MGR,EVENT_TESTING,5
<--table perfevents ends-->

I have set the QueueName column to be the unique identifier as it is the unique MQ object I am trying to monitor. Unfortunately the first occurrence of the unique column identifier, in my case the QueueName, masks any other occurrences and as such AdventNet is missing these alert conditions. The first condition, MQRC_Q_DEPTH_HIGH, is a warning however the MQRC_Q_FULL is a critical alert which is missed.

Is there a way to still use the QueueName as the unique column identifier but not have the first occurrence mask all other occurrences in the output file? It is also possible that an event may have a critical state that is cleared in the same output file.










                New to ADSelfService Plus?