| I'm not too sure what your asking.
Do you mean that the GETEVENT directive entered at the FCL displays
*your* event report,
but when you write an alarm rule (occurs function) none of *your* event
report is displayed by the resultant Alarms 'rule fired' event ??
Whew - with that said -
If this is the case .. Currently the Alarms GETEVEMT directive does not
return (in out-p) any of the argument data from your originating event.
The Alarms GETEVENT directive 'Evidence' record contains some information
about the Data-that-caused-the-rule-to-fire:
o Entity (FullEntityName)
o Data (Latin1String)
o Timestamp (BinAbsTime)
In the case of the Rule written on an attribute ...
Expression = (node4 foo max addr > 50)
The Evidence.Data field would contain "Maximum Address = 1023"
(or whatever the real attribute value was)
In the case of the Rule written on an Event ...
Expression = (OCCURS(node4 foo Counters Zeroed))
The Evidence.Data field would contain "Counters Zeroed has occured..."
--------------
Here is some sample output from the Alarms GETEVENT directive written on
the 'new for v1.2' PONG directive - The 'Pong Timeout' event has an argument,
(Acceptable Response Time) but it is not retained by the Alarms package 8(
MCC> getevent mcc 0 alarms rule keith any notif event
MCC 0 ALARMS RULE keith
AT 3-SEP-1991 12:39:30 NOTIFICATION EVENTS
Alarm Event Received
Alarm Rule Fired
EVIDENCE = { ( entity = Sample ETHRFX_NS:.dflat ,
data = "Pong Timeout has occurred 3-SEP-1991 12:39:29.38",
timestamp = 3-SEP-1991 12:39:29.38 ) }
Expression = (occurs(sample .dflat pong timeout))
Perceived Severity = indeterminate
|