|
From: | Martin Pala |
Subject: | Re: monitoring status patch (Oliver's patch from 3.2.2003) |
Date: | Tue, 11 Feb 2003 15:06:44 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021226 Debian/1.2.1-9 |
Oliver Jehle wrote:
-1 for the do_validate... i think, monit should always monitor a process when its running...Monit supports both behaviors - if you want to monitor the process forever (regardless of the failure rate) you don't need to use 'timeout' statement.if monit dies and restarts all processes are in status not monitoringalready running and thats bad.
If the process reaches erroneous state and monit detects the failure say 3 times of every 5 attempts, you will be noted about every failure every monit cycle, which for someone isn't suitable - you know that the process reached 'hard' error and it makes no sense to monitor it until it will be solved by hand.
For such cases (or deployments) is 'timeout' statement here. If you will use it, monit will stop monitoring after custom failure ratio is reached. It is important to keep the state of monitoring (do_validate flag) between monit reloads for this purpose.
If you don't use timeout statement, monit will never disable monitoring (don' have any reason for it) and in that case is assertion "monitor every running process" correct.
Cheers, Martin
[Prev in Thread] | Current Thread | [Next in Thread] |