[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Periodic Heartbeat EMails

From: Paul Tiseo
Subject: Re: Periodic Heartbeat EMails
Date: Fri, 27 Jan 2017 19:29:32 +0000

Exactly. I don't want to add another layer of monitoring so that I can monitor the monitor. ;)

cron would be acceptable as a fallback if monit can't do it, I guess, except that I have to add another potential point of failure to be able to get emails out, ultimately to or through our mailserver, which is Gmail. I'd need some mail client of some sort.

m/monit seems like a "pricey" tool to have a worker that runs two small Node apps get me a heartbeat email (although I understand it's value in more complex scenarios)

Since monit can email, I was hoping to lasso it into serving me up a heartbeat, but it seems it can't do it. It will email me on state transitions only, which I get is the design intent.

PS: I had setup a heartbeat based on a check for a file that doesn't and will not exist, but it sends an ominous, alert-y email. :) Fine for me, but now I have to explain to others to not ignore alerts except one... yeah, minor thing, but I like to avoid death by a thousand cuts. :)

On Thu, Jan 26, 2017 at 10:48 AM Guillaume François <address@hidden> 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.

Like they says on some movies: 
bodyguards: "we are going to protect you VIP."
VIP "Ok but who is gonna to protect you (bodyguard)" 

2017-01-26 16:29 GMT+01:00 Geoff Goas <address@hidden>:
Is the "heartbeat" just a periodic email? Why not put that in a cron job?

On Wed, Jan 25, 2017 at 11:36 AM, Tino Hendricks <address@hidden> wrote:
Just out of curiosity, what is the benefit of having mails sent to you regardless of the system state?
I always consider it the biggest advantage of a monitoring that it _alerts_ you actively in case of emergency.

Am 23. Januar 2017 um 17:59:56, Paul Tiseo (address@hidden(mailto:address@hidden)) schrieb:

> So, I set monitrc to the below. Not sure where I am to add the "reminder" clause so that the heartbeat service is the one that emails me without fail (don't want this to apply to other services). Suggestions?
> set daemon 60 with start delay 15
> set logfile /apps/monit.log
> set pidfile /apps/
> set idfile /apps/
> set statefile /apps/state
> set mailserver port 587
> username "address@hidden(mailto:address@hidden)" password "aaa"
> using tlsv12
> set httpd port 2182
> allow aaa:aaa
> signature disable
> set alert address@hidden(mailto:address@hidden)
> #-- HEARTBEAT ---------------------------------------------------------
> check host agp-heartbeat address every 2 cycles
> if failed ping then alert
> else if succeeded then alert
> --
> Thanks.
> _______________________________
> Paul Tiseo, address@hidden(mailto:address@hidden)

Geoff Goas
Systems Engineer

To unsubscribe:

Version: 3.1
GCS/IT d(+) s++:- a C++$ ULC(+)>+++$ !P--- L+>$ !E---? W+++$ !N* !o-- K--? w(+) !O---? !M- !V--? PS+? !PE Y+ PGP++>+++ !t-- !5 !X- R(+)>++* tv-? b(-) DI !D- G(+)>+ e+++ h--() r->$ y?*
To unsubscribe:

Paul Tiseo, address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]