#Azure Alert fires multiple times

1 messages · Page 1 of 1 (latest)

fiery stump
#

Hi, I created some Alert rules for my AKS and used a metric alert with a dimension and threshold: the alert rule should trigger whenever there is a failing pod.
I recognized this morning, that the monitor alerts are flooded because over the weekend, there were some pods failing.
Shouldn't the alert be updated instead of creating new ones?
Is this the standard behavior (even for log alerts?)? I'm thinking about moving my metric alerts to log alerts (because the metric alerts don't disappear, only after 30 days as I read!!), but will this also prevent "duplicated alerts" every 5 minutes?
To be honest, I don't want to create my custom queries for this. The metric alert is actually what I need.. but the behavior of it is not very friendly to our devs (because of the long life and duplication).
Has someone some ideas about this?

Hint: It would be awesome if I could reuse queries from my workbook! 🙂

verbal rose
#

One setting "resolves" the alert if enough time has gone by in the acceptable metric area

#

So if something is failing and getting healthy and failing, it will produce a lot of alerts

#

But if it fails and keeps failing, then only one alert will every be made

verbal rose
#

It is the only thing I could think of

fiery stump
#

Me too so I try it out

verbal rose
#

Do you get what I am saying about them tho?
They will "auto resolve" so there is a potential for many errors if the service gets healthy within the time period

#

I was hella confused by them at first

fiery stump
#

your second sentences confuses me a little bit though 😄 Why is there a potential for many errors if the service gets healthy?