|Subject:||Re: monit unmonitor sends too many alerts on unmonitor/monitor|
|Date:||Wed, 5 Sep 2012 16:42:46 -0700|
Hi,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).Regards,Martin--I am bringing up an issue that was previously brought up on another thread.
The complaint is: http://osdir.com/ml/monit-general/2008-06/msg00020.html
The solution is to just filter monitor and unmonitor commands http://osdir.com/ml/monit-general/2008-06/msg00023.html
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?
|[Prev in Thread]||Current Thread||[Next in Thread]|