The "Connection" event is related to Monit's port test. The heartbeat event is labeled "Monit reachable" in the Events menu.
Regards, Martin On 24 Jul 2014, at 15:27, Rich Sutton <[email protected]> wrote: > Martin. > > I've got a working mail server set up, but I can't seem to get the right > alert rule written for this. > > I've got: > > If any of the following conditions are met: > Any Host -> Service monit -> Failed -> Connection > Then perform the following action: > Send mail to address -> [email protected] > > Is that correct? > > > Rich Sutton > CTO / VP of Engineering > mobile 714-318-7737 > nexgate.com > > > > On Wed, Jul 23, 2014 at 9:55 PM, Martin Pala <[email protected]> wrote: > Hi Rich, > > M/Monit generates heartbeat event automatically in such case (by default if > Monit didn't report for 3 cycles) - just set an alert rule and a mailserver i > the Admin page. > > Regards, > Martin > > > On 24 Jul 2014, at 03:06, Rich Sutton <[email protected]> wrote: > >> Hi, >> >> I'm using M/Monit with about 50 nodes. Monit on the nodes is working well to >> sending email alerts, but (rarely) the monit daemon crashes. >> >> How can I configure M/Monit to send an email alert when it hasn't heard from >> a monit daemon for some number of minutes? >> >> Rich Sutton >> CTO / VP of Engineering >> mobile 714-318-7737 >> nexgate.com >> >> -- >> To unsubscribe: >> https://lists.nongnu.org/mailman/listinfo/monit-general > > > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general > > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general
-- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
