Hi Jan, Yes I have been reading the manual - it just gets slightly confusing when you have the statement alert as an action and also use the keyword alert for setting the mail address. The same is true of having an alert option of timeout but not unmonitor. For example I only care about alerting where I have specifically said to alert for that services and only to the email address I have specified. Conversely I do also use mmonit which is hopefully tracking all state changes but I want the alerting handled locally by each server.
Mark > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On > Behalf Of Jan-Henrik Haukeland > Sent: 05 October 2011 17:04 > To: This is the general mailing list for monit > Subject: Re: restart after cycles > > > On Oct 5, 2011, at 5:43 PM, Mark Olliver wrote: > > > Now I just need to have it not alert for the other events > > This is documented at > http://mmonit.com/monit/documentation/monit.html#alert_messages [1] > > For instance 'alert foo@bar only on { timeout, nonexist }' or the negation > 'alert foo@bar not on { action, instance, pid, ppid }' That last version will > prevent that Monit sends an alert every time it start or stops and whenever > you issue an action on a service, such as start, stop, restart (un)monitoring > and when a process's pidfile changes. > > [1] I know it may be hard to read the manual and find the information you > need. So we plan to instead create a simple "how to" or FAQs to make all the > things you can do with Monit more accessible. We'll notify this mailing list > when the new improved docs are available. > > > > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general -- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
