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 |
- [jffnms-users] Problem with Output during Trigger Proces... Tim Carr
- Re: [jffnms-users] Problem with Output during Trigg... Javier Szyszlican
- RE: [jffnms-users] Problem with Output during Trigg... Tim Carr
- Re: [jffnms-users] Problem with Output during T... Javier Szyszlican
- RE: [jffnms-users] Problem with Output during Trigg... Tim Carr
- Re: [jffnms-users] Problem with Output during T... Javier Szyszlican