I'm in the process of building an Asterisk ZenPack, and to start I wrote a simple Nagios-style monitoring script to monitor the status of a PRI span. The script is setup as a COMMAND data source of severity error, and the script itself works just fine, but when I manually down a PRI to test it I end up with info events and thus I never get paged.

The script is a bit long to paste here but the import bit is this:


Code:
if ($up) {
   print "SPAN UP\n";

   exit(0);
}
else {
   print "SPAN DOWN\n";

   exit(2);
}



(the ommited code basically logs into Asterisk and does some commands to set the $up variable appropriately.)

I understand that what SHOULD be happening is that with an exit code of 2, it should generate an event of (severity + 1), which in my case should be CRITICAL. And in fact, if I run zencommand from the command line with verbosity turned on, I can see that it does indeed claim it is generating a critical event, but when I go to the interface, it's an info event! What on Earth is going on here?

Is it possible that event class this event is going into has zEventSeverity set to info?

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to