Hi Attila, two things. First, what type of alert conditions are you
using? Certain conditions, most notably Availability conditions like
GOES DOWN, ignore dampening because they are discrete events. Second,
there was a recent bug fix in the area of dampening. The hourly data
purge was negating some of the dampening state, so dampening that
crossed the top of the hour may have been affected. This fix will be in
4.10.
Do either of these things, maybe explain what you are seeing?
Also, you are saying that this is dampening at the alert template
level? Check to ensure the dampening is also reflected at the resource
level by looking at the alert definition that was propagated down from
the template to one of the resources of the relevant type.
On 11/27/2013 4:35 AM, Attila Heidrich wrote:
No one encounters similar? It is proven, that I can set anything in
the dampening section, I will get each and every alerting mail! Very
annoying, tbh...
What to chack if I set it correctly (I think there's nothing I can
miss, it's quite simple - and I have also seen this work)? Or any log
that should be correlated?
Attila
2013/11/8 Attila Heidrich <attila.heidrich(a)gmail.com
<mailto:attila.heidrich@gmail.com>>
Hi!
It seems that there's no use to set any dampening for the alert
tamplates, I got all alerts for any of them.
I usually use "one for several hours"... practically I only use
templates, so the servers inherits the settings.
Is there any trick I miss? I have used 4.8 only a few days long,
but as far as I can remember, it worked as I expected.
Attila
_______________________________________________
rhq-users mailing list
rhq-users(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-users