Re: [Nagios-users] State Stalking and notifications
On Feb 20, 2008, at 7:46 AM, Frost, Mark {PBG} wrote:
> I had thought about writing a custom check for each line
> of output that this command generates, but that seems needlessly
> painful.
You could write one active check that parses the output, figures out
what's gone wrong, and then submits passive results for the specific
services that have errors.
Mike
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Nagios-users mailing list
Nagios-users@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
Re: [Nagios-users] State Stalking and notifications
[EMAIL PROTECTED] wrote: > > I had thought about writing a custom check for each line > > of output that this command generates, but that seems needlessly > > painful. [...] > > I'm guessing the answer here is "Nagios can't do that", but I thought > > I'd ask anyway. > > 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. If you need both granularity and flexibility and on top an overall evaluation of your particular results then have a look onto check_multi (http://www.my-plugin.de/check_multi). It combines both concepts - granular results and process views - just as you define it. -Matthias - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] State Stalking and notifications
[EMAIL PROTECTED] 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. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] State Stalking and notifications
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:nagios-users-
> [EMAIL PROTECTED] On Behalf Of Frost, Mark {PBG}
> Sent: Wednesday, February 20, 2008 9:46 AM
> To: Nagios Users Mailinglist
> Subject: [Nagios-users] State Stalking and notifications
>
>
> 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
> 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.
Nagios can't do that.
However, you can but it's not necessarily convenient. I would approach
it as having intimate control over the notification script. It's
certainly possible to specify a notification script for that service
that tracks the previous output, status and other information and
notifies appropriately. Combine that with the volatile setting and you
have a way to do what you want outside of nagios.
--
Marc
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Nagios-users mailing list
Nagios-users@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
[Nagios-users] State Stalking and notifications
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 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Nagios-users mailing list Nagios-users@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
