On 26 January 2017 at 10:44, Guillaume François <[email protected]> wrote: > I suppose the goal is to ensure, monit is able to report issue -> up and > running and SMTP functionnal. > > Let's suppose one of these two "dies" for any reason, an issue raises but > you get never notified cause you are not aware that the system is down. > > Having regular heartbeat from the monitoring system helps to know that it is > up and running. > > Again it just a personal guess but i can understand the need.
If this is all you need cron a "monit monitor <something>", a generic check of some kind that would never time out. Maybe the default system one? ## Check general system resources such as load average, cpu and memory ## usage. Each test specifies a resource, conditions and the action to be ## performed should a test fail. # # check system $HOST # if loadavg (1min) > 4 then alert # if loadavg (5min) > 2 then alert # if cpu usage > 95% for 10 cycles then alert # if memory usage > 75% then alert # if swap usage > 25% then alert -- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
