[Pacemaker] Finer control over when email is sent?

Andrew Beekhof andrew at beekhof.net
Mon Jun 11 19:43:15 EDT 2012


On Wed, Jun 6, 2012 at 9:08 AM, Peter Skirko <peter at mixpanel.com> wrote:
> Looking at the source, it seems like the assumption is to just wire up an
> external program to do the notifications for you, that way you can send
> whatever you do or don't want.

Basically.
We might include some filtering capabilities in the future, but there
is not a lot of bandwidth to work on it at the moment.

>
> Thanks,
> -Peter
>
>
> On Tue, Jun 5, 2012 at 3:37 PM, Peter Skirko <peter at mixpanel.com> wrote:
>>
>> Hi,
>>
>> We are using pacemaker 1.0.8 and heartbeat 3.0.3 on ubuntu 10.04. We are
>> currently sending mail from crm_mon as follows:
>>
>> crm_mon --daemonize --mail-to foo at mixpanel.com --mail-host localhost:25
>>
>> My question is: is it possible to exert finer control over which emails
>> are actually sent?
>>
>> For example, we have ping resources that are checking the health of
>> various network interfaces. Right now, we are receiving emails for start,
>> monitor, and stop events for these resources, but we don't want these
>> emails. We just want emails relating to failures, and just to start and stop
>> events on our IP addresses?
>>
>> I checked the documentation and man pages and didn't see anything
>> immediate, but I wanted to make sure I hadn't overlooked any options.
>>
>> Thanks,
>> -Peter
>
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>




More information about the Pacemaker mailing list