[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: pagerduty integration with M/Monit
From: |
Christopher Wood |
Subject: |
Re: pagerduty integration with M/Monit |
Date: |
Tue, 10 Feb 2015 15:30:19 -0500 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Tue, Feb 10, 2015 at 12:19:16PM -0800, Paul Theodoropoulos wrote:
> I'm trying to use pagerduty for alerting. I use M/Monit as the
> one-stop gateway for all alert management. Since I'd rather not have
> to modify several hundred monitoring rules across many servers, I've
> tried using the 'execute program' action in M/Monit to trigger
> alerts via the pagerduty API. It works - sort of. If I use
> "/usr/local/bin/pagerduty-trigger $MONIT_SERVICE", it'll send me an
> alert if I kill off crond for example. But...it reports that crond
> failed...on my M/Monit server, rather than the source server. If I
> use $MONIT_HOST - well, then it reports "localhost failed on (my
> monit server)".
Concatenation?
/usr/local/bin/pagerduty-trigger "${MONIT_SERVICE}__${MONIT_HOST}"
There, single param.
> The pagerduty trigger/resolve scripts only take one argument. Their
> integration page:
> http://www.pagerduty.com/docs/guides/monit-integration-guide/
>
> Thoughts?
>
> --
> Paul Theodoropoulos
> www.anastrophe.com
>
>
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general