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)".
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
