Are you matching by Alarms or Event?
If its alarm then you better do a var_dump or debug of the variables because we
include 2 events in the parameter the start and the stop, and you may not be
asking for the correct one.
Javier
Tim Carr wrote:
I’ve got a question about the output of text when triggers are being
processed. Specifically, the text that is coming out of the trigger,
when an event is closing, does not match the text that is showing up in
the event log in the JFF browser view. This is relating to the
$event[text] field.
For example, when an interface goes down, the browser view of what the
event is states:
TCP/UDP Service Port 80 1 closed (Unknown Customer http)
The output from the $event[text] processing in the trigger I created is:
TCP/UDP Service Port 80 1 closed (Unknown Customer http)
Those two match up. But…when that interface comes back up, the browser
view of what the event is states:
TCP/UDP Service Port 80 1 open (Unknown Customer http)
But the output from the $event[text] processing in the trigger is:
TCP/UDP Service Port 80 1 closed (Unknown Customer http)
It looks like the “everything is now ok” event still shows the interface
to be down. Is this expected behavior?
Thanks,
Tim Carr
Buchanan Associates
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Javier Szyszlican, Project Leader, JFFNMS
[EMAIL PROTECTED]
I hope JFFNMS or I were helpful to you, if you
can, please donate at http://jffnms.org/donate
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
jffnms-users mailing list
jffnms-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jffnms-users
