State Stalking and notifications

[mark.potter at academy.com]

nagios-users-bounces at lists.sourceforge.net wrote on 02/20/2008 09:46:12 
AM:

> 
> On more than a few occasions, I've had users ask me if it's possible to
> have alerts sent if the output of a check changes.  That is, if you
> consider that a check might actually have multiple failure conditions it
> could be monitoring.  And example of this might be a single command you
> run that reports about multiple aspects of an application.  The check
> goes critical if one part of that app becomes non-functional, but if a
> second piece goes off-line, the state of the check hasn't changed, so no
> notification is sent.
> 
> I read about "state stalking" and thought that this might be what I was
> looking for.  However, after reading a bit more closely, it appears that
> what state stalking is really about is logging results of checks and not
> about sending additional notifications.
> 
> I understand the philosophy of "well if one part is broken or two parts
> are broken, you have to fix it anyway".  There's also the hack of having
> recurring notifications sent (say every 30 minutes) which should send a
> user the latest check output.  Neither of those options are particularly
> nice for us.  I had thought about writing a custom check for each line
> of output that this command generates, but that seems needlessly
> painful.
> 
> I see that volatile checks are more about notifications, however they
> will send a notification every time the service comes back non-OK (i.e.
> even if the check output is exactly the same) which is not what we want.
> 
> I'm guessing the answer here is "Nagios can't do that", but I thought
> I'd ask anyway.
> 
> Thanks
> 
> Mark
> 

Technically Nagios can't do that. At least not from the vantage point you 
have described. We are much more granular in our monitoring for exactly 
the scenario you have described. At this point we don't combine multiple 
pieces into a single service check unless a department manager 
specifically requests a full overview in a single check. We monitor each 
piece with its own service check so we have complete control over who get 
notified for what, when they get notified, how often they get notified, 
and so on. I would say that Nagios can do what you want but that it is up 
to you to make your checks more granular.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080220/a40f02ae/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- next part --------------
_______________________________________________
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