Alert based on response?

[Jason Frisvold]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kyle O'Donnell wrote:
> i would create a custom notification command that does an eval on the
> $SERVICEOUTPUT$ before issuing /bin/mail.
> 
> then create a contact to use that new notification command.

Ok, that handles notification, but the object would still show as
warning/critical in the web interface with (likely) a generic name.  For
my UPS example, you'd have the "UPS Status" service in a warning or
critical state, but nothing else to go on...

Or should I create a custom check_snmp plugin that reports meaningful
info for status information rather than just a generic message like
"SNMP CRITICAL - *4*" ....

It seems this will end up with me writing lots of plugins/notification
commands customized for each type of service/alert...  Before I go down
that path, I wanted to make sure there wasn't a more generic method for
handling this.

Thanks!

- --
- ---------------------------
Jason Frisvold
Network Engineer
frisvolj at lafayette.edu
- ---------------------------
"What I cannot create, I do not understand"
   - Richard Feynman
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org

iD8DBQFJwnvzO80o6DJ8UvkRAgLjAJ4jDDhBuNZmDSmjgGYNCpa0otPWCACfS30Y
jdBSteifzmXuOehurEIHEJQ=
=eIjW
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null