-
- Influencer
- Posts: 23
- Liked: 3 times
- Joined: Jul 10, 2015 9:18 am
- Contact:
Alarm "Time Period" is ignored not working
Hello,
I have the latest version of 9.5 with Update 1.
I have a custom Alarm in which I want to monitor the "CPU usage" from the VMs over 60 minutes.
It should generate an warning if the Aggregation "Avg" is above 30% after 60 Minutes.
And an error if the Aggregation "Avg" is above 60% after 60 Minutes.
Unfortunately the "Time Period" is totally ignored and it just takes 15 minutes as "Time period".
Is this a Bug or limitation of the Version 9.5, because it worked in the Version 9 as expected.
Any ideas?
Thank You
Michael
I have the latest version of 9.5 with Update 1.
I have a custom Alarm in which I want to monitor the "CPU usage" from the VMs over 60 minutes.
It should generate an warning if the Aggregation "Avg" is above 30% after 60 Minutes.
And an error if the Aggregation "Avg" is above 60% after 60 Minutes.
Unfortunately the "Time Period" is totally ignored and it just takes 15 minutes as "Time period".
Is this a Bug or limitation of the Version 9.5, because it worked in the Version 9 as expected.
Any ideas?
Thank You
Michael
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Alarm "Time Period" is ignored not working
Hello Michael,
That sounds like a bug. What product version are you at?
Thanks!
That sounds like a bug. What product version are you at?
Thanks!
-
- Influencer
- Posts: 23
- Liked: 3 times
- Joined: Jul 10, 2015 9:18 am
- Contact:
Re: Alarm "Time Period" is ignored not working
I am on the following Version: 9.5.0.3254
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Alarm "Time Period" is ignored not working
Talked to QA team and it turned to be a known bug. Support team has a hot fix for it so please contact them.
-
- Influencer
- Posts: 23
- Liked: 3 times
- Joined: Jul 10, 2015 9:18 am
- Contact:
Re: Alarm "Time Period" is ignored not working
Thank You for the infos.
My Case Number is 02251948.
Perhaps you can me send me a link for the Hot Fix.
Thank You
Michael
My Case Number is 02251948.
Perhaps you can me send me a link for the Hot Fix.
Thank You
Michael
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Alarm "Time Period" is ignored not working
Hot fixes are distributed from support engineers, not via direct links. So please keep working with the support team.
-
- Influencer
- Posts: 23
- Liked: 3 times
- Joined: Jul 10, 2015 9:18 am
- Contact:
Re: Alarm "Time Period" is ignored not working
Hello Shestakov,
this is what support gave me.
In short, this is the algorithm currently used for Time Period on Counter-based Alarms:
1. Pick a counter-based alarm.
2. Take note of all alarms that use this very counter and find the one with the lowest Time Period value set.
3. In the registry editor's Veeam ONE key find UsageTriggerIntervalAccuracy value.
4. Divide the lowest Time Period value set from p.2 by UsageTriggerIntervalAccuracy value from p.3 to get the time period used for measuring the average counter value.
5. Each alarm with the counter in question uses a certain amount of averaged points calculated in p.4 that corresponds to the Time Period value in a specific alarm (there may be more that one as per p.1) and calculates the average of them in it's turn.
6. If the average value out of those averaged points exceeds threshold - the alarm is triggered, if not - the alarm is not triggered.
7. So, regardless of what Time Period is set for the alarm, the condition will be checked every point in time calculated in p.4. The Time Period setting only affects a certain amount of intermediate averaged points, that are used for calculating the final average value with the Time Period set and is compared with the threshold set (In other words, the Time Period setting is not the delay that affects alarm triggering, but a period that sets the amount of averaged points as per p.4).
I doublechecked with modelling and there the alarm-rule is working as expected.
Only in real world there seems to be a bug, that there is only taking the last 15 minutes as sampling value.
Can you tell support to give me the hot fix?
Thank you
this is what support gave me.
In short, this is the algorithm currently used for Time Period on Counter-based Alarms:
1. Pick a counter-based alarm.
2. Take note of all alarms that use this very counter and find the one with the lowest Time Period value set.
3. In the registry editor's Veeam ONE key find UsageTriggerIntervalAccuracy value.
4. Divide the lowest Time Period value set from p.2 by UsageTriggerIntervalAccuracy value from p.3 to get the time period used for measuring the average counter value.
5. Each alarm with the counter in question uses a certain amount of averaged points calculated in p.4 that corresponds to the Time Period value in a specific alarm (there may be more that one as per p.1) and calculates the average of them in it's turn.
6. If the average value out of those averaged points exceeds threshold - the alarm is triggered, if not - the alarm is not triggered.
7. So, regardless of what Time Period is set for the alarm, the condition will be checked every point in time calculated in p.4. The Time Period setting only affects a certain amount of intermediate averaged points, that are used for calculating the final average value with the Time Period set and is compared with the threshold set (In other words, the Time Period setting is not the delay that affects alarm triggering, but a period that sets the amount of averaged points as per p.4).
I doublechecked with modelling and there the alarm-rule is working as expected.
Only in real world there seems to be a bug, that there is only taking the last 15 minutes as sampling value.
Can you tell support to give me the hot fix?
Thank you
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Alarm "Time Period" is ignored not working
Sure, I`ll talk to the support engineers and let you give you more info.
-
- Influencer
- Posts: 23
- Liked: 3 times
- Joined: Jul 10, 2015 9:18 am
- Contact:
Re: Alarm "Time Period" is ignored not working
Thank You Shestakov.
After applying the hotfix, all is working as expected.
Thank You
Michael
After applying the hotfix, all is working as expected.
Thank You
Michael
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Alarm "Time Period" is ignored not working
Great to know. Thanks for updating!
Who is online
Users browsing this forum: Baidu [Spider] and 11 guests