[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Performing an action only after X failures

From: Martin Pala
Subject: Re: Performing an action only after X failures
Date: Wed, 29 Dec 2004 14:09:39 +0100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910

Jan-Henrik Haukeland wrote:

On Dec 26, 2004, at 21:26, Martin Pala wrote:

In the case that it will be general, it can allow to stack the rules and provide error level dependant actions, such as for example:
 # if <X> <EVENT> within <Y> cycles then <ACTION>

... <X>     = number of event occurences
... <EVENT>     = event type
... <Y>     = number of consequent cycles
... <ACTION>    = given action (alert|restart|unmonitor|exec|...)

I'm +1 to add such feature. What do developers and users think about it?

I'm +1. If implemented then I think we can remove the every-statement?

Maybe the every-statement could be still useful - for services which you purposely for some reason don't want to test in every cycle.

For example in the case that monit is set to run tests every 5 seconds, but there is some service which is sufficient to test once per every 15 minutes, you can skip intermediate cycles (and save related time and resources).

However, i don't use this approach (skip cycles) in practice and currently can't imagine any good real life example ;)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]