[ZBXNEXT-1565] maintenance windows or changes to escalations should apply to events which began before the maintenance window Created: 2013 Jan 10 Updated: 2016 Feb 26 Resolved: 2016 Feb 22 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Server (S) |
Affects Version/s: | 1.8.15 |
Fix Version/s: | None |
Type: | Change Request | Priority: | Major |
Reporter: | Will Lowe | Assignee: | Unassigned |
Resolution: | Duplicate | Votes: | 1 |
Labels: | actions, escalations, maintenance | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
Description |
Imagine a host experiences an event at 5pm, and a maintenance window is scheduled from 5:30 to 6pm. In Zabbix today, the event will still produce alerts between 5:30 and 6pm because the event happened before the Maintenance window began. Instead, we would like the maintenance window to suppress those alerts. A similar workflow seems to happen for changes to escalations and actions: changes to the escalation or action do not apply to events which happened before the change. Often this leaves us no way to get an event to stop alerting except to manually modify the database. It would be ideal if escalations and actions were evaluated each time, rather than only when the event is created. |
Comments |
Comment by Ashwani Kumar [ 2013 Jan 18 ] |
Hi, Till we get a fix for this problem, can we get a workaround ? like some scripts which we manually execute on server to stop the escalation ? Reagrds, Ashwani |
Comment by richlv [ 2013 Jan 18 ] |
please use zabbix forums, irc and other channels for community support see https://zabbix.org/wiki/Getting_help for more detail |
Comment by Sven Win [ 2013 Mar 11 ] |
I cannot find any help on this subject in the forums. This problem is a serious show stoppper. Is there a work around for this? |
Comment by itcbsops [ 2016 Feb 15 ] |
Hi, I have opened a similar case as well. And this behavior annoys us too. The workaround, if I remember well, is to disable the host and enable it again afterwards. This would cause the Action's escalation steps to stop counting, and the e-mails to stop being sent. @Zabbix : apparently, we aren't the only ones to require this to be fixed. Any idea when that is planned ? |
Comment by Oleksii Zagorskyi [ 2016 Feb 20 ] |
Issue summary in other words, IMO: Would you agree to update the summary ? |
Comment by Aleksandrs Saveljevs [ 2016 Feb 22 ] |
Adding maintenance status condition for operations is requested in |
Comment by itcbsops [ 2016 Feb 22 ] |
Aleks, I'm afraid there is already such a condition but it is ignored because the action is not evaluation during maintenance, which makes the option/condition useless in fact |
Comment by Aleksandrs Saveljevs [ 2016 Feb 22 ] |
it.sdm, there is indeed such a condition, but it is available for actions, not operations. |
Comment by Oleksii Zagorskyi [ 2016 Feb 22 ] |
I'd closed this one as duplicate of |
Comment by itcbsops [ 2016 Feb 22 ] |
Aleksandrs , Got your point. Thanks |
Comment by Oleksii Zagorskyi [ 2016 Feb 22 ] |
Closing as duplicate. |