[Top][All Lists]

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

Re: monit unmonitor sends too many alerts on unmonitor/monitor

From: Zippy Zeppoli
Subject: Re: monit unmonitor sends too many alerts on unmonitor/monitor
Date: Wed, 5 Sep 2012 16:42:46 -0700

I think you may have misunderstood.
I only want to filter unmonitor commands which are done via a script, so I'd like to pass a --quit or --silent flag which suppresses alerts.

When a human performs an unmonitor, then they would not pass this flag, and alerts would be generated, so you know it was done manually.

On Wed, Sep 5, 2012 at 2:10 AM, Martin Pala <address@hidden> wrote:

the "action" filter will filter out the all actions which were triggered manually: either via the HTML interface or via the command line (such as "monit restart myservice") - not just monit+unmonitor, but also start+stop+restart.

The actions which are triggered internally as a result of matching testing rule are still send (they can be filtered out by specific filters too, but the "(manual) action" filter won't stop it - see manual for more details).


On Sep 4, 2012, at 8:44 PM, Zippy Zeppoli <address@hidden> wrote:

I am bringing up an issue that was previously brought up on another thread.

The complaint is:

The solution is to just filter monitor and unmonitor commands

It would be great if there was a way to silence automated monitor and unmonitor calls, such as those that are referenced from an automated script.

Right now, if I filter, I will never know if a human monitored or unmonitored a script due to this filter, although my actions will be filtered, which will reduce the chatter. Is there a way to have the best of both worlds? Such as call unmonitor via a flag, such as --silent?
To unsubscribe:

To unsubscribe:

reply via email to

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