List members,
About two weeks ago Bill Fisher answered my question about the different event
severities. Based on the way I understood his response I had our IM-pro create
a custom command line probe based on the probe provided by Dartware.
We replaced the exit code definitions with an expanded section. The goal is to
allow separation between the network/OS caused errors and the errors reported
about the application. I'm not part of the network or OS teams and do not need
to be alerted about things I can not fix.
This is the exit code section in our probe:
<command-exit>
critical:${EXIT_CODE}=6
alarm:${EXIT_CODE}=5
warning:${EXIT_CODE}=4
okay:${EXIT_CODE}=3
down:${EXIT_CODE}=2
down:${EXIT_CODE}=1
up:${EXIT_CODE}=0
</command-exit>
It is not working as expected. The only exit codes it recognizes is 0 and 1.
Everything else causes a ? icon. We tried removing the double definition of
down without any improvement.
Is it possible to have the command line probe run a nagios type script, via
nrpe, on a remote system and understand severities beyond up and down?
Thanks,
Rich
[EMAIL PROTECTED]
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
