Veeam 9 -Alarm Suppression Broken-

[mbietz]

Hello,

Since I upgraded to Veeam 9.0.0.206 last week (9.2.2015) the alarm suppression is not working as it did before with Veeam 8.

I have used very much alarm suppression to fine tune the monitoring.

For Instance:
I have an alarm created which raised a warning if the "write I/o" is above 250 for one hour.
I suppressed that alarm daily from 7:00 - 9:00 for one vm.

it bugs me with a warning at 9:00:10 that the I/o is above threshold, but if I look in the performance charts for this counter, there is no write I/o from 8:00 - 9:00.
There is heavy I/o between 7:00 - 8:00, but that should not take into account.
Well I doubled checked that behaviour on a dozens alarms which I createtd, and it is always the same.
In Veeam 8 this worked like a charme, it seems to be broken in Veeam 9.
Is there a fix for this?

Thank you.

Michael Bietz

[Vitaliy S.]

Michael,

Alarm suppression should not have been changed. Can you please open a support case and let us know your case ID?

Thanks!

[mbietz]

Hello Vitaliy,

I opened a case for this #01699925

Thank you

Michael

[mbietz]

i got an respond to that case.

here it is.

"The issue is caused by new alarming mechanism design in Veeam ONE v9 that depends on setting of Time period.
Now, it is counting average values for the Time period intervals.
According to your performance chart, on 9:00 the suppress ended and we try to find last point for the last hour. It happens so, that the last found point was nearly on 8:20 and its value for the last hour (7:20 - 8:20) is about 300.

To resolve this issue you can try one of these:
1. in the rules of he alarm add second trigger with the same counter, but smaller Time period (15 min)
2. or increase suppress time period to 9:40"

for me it is okay, and helpful to know how it works, so that i can take that into planning with creation of suppressions.

[Vitaliy S.]

Michael, I have discussed this situation with our dev team. We will investigate possibilities of not having dependencies on Time Period parameter when detecting threshold breaches.