Re: [munin-users] Suppressing contact emails

[Bjørn R. <bj...@ru...>]

On 29. des. 2013 19:23, Martin N Brampton wrote:
> Hi
>
> I'm struggling to control email alerts.  Running the standard munin from
> Debian Wheezy repository.  Following the sample configuration, one of my
> monitored servers has an entry:
>
> address *.*.*.*		# real address hidden by *
> diskstats.contacts no   # Don't warn if the 'diskstats' plugin exceeds
> warning values.
> use_node_name yes
>
> But I'm still getting emails when there is a spike in the wait time for
> a disk.

If your diskstats plugin is the same as mine, it's a multigraph plugin. 
In that case I think you'll need to suppress the alert with the specific 
"section" of the multigraph plugin, probably diskstats_latency.

> On a similar topic, I probably know the answer, but is it correct that
> currently there is no way to send warning emails to a different email
> address from critical emails?
>

It'll probably work but might require some work. I have not tested this. 
Try this in munin.conf on the master:

1) Define two logically named contacts, e.g.
contact.warnmail.command mail -s "Munin warnings" war...@ex...
contact.critmail.command mail -s "Munin critical alerts" 
cri...@ex...

2) Define the defaults, as somewhat cryptically documented in 
http://munin-monitoring.org/wiki/munin.conf: 
contact./contact/.always_send [warning] [critical] . So in this case:
contact.warnmail.always_send warning
contact.critmail.always_send critical

3) Note the explanation of always_send: "Always send messages with a 
state that is mentioned. Enabling this tells munin-limits to spam you 
even if the state didn't change since previous run." In other words, 
prepare your inbox filters.

4) For every node or plugin you don't want to do as instructed above, 
you'll need to override the settings using "contacts no" for disabling 
completely or by setting another contact you've defined.

Please let us know if this really works :-)

-- 
Bjørn