[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:
Duplicate
duplicates ZBXNEXT-128 New condition for operations: host is... Closed
is duplicated by ZBX-6147 stop escalation imidiatly Closed
is duplicated by ZBX-10178 action sends e-mails while host is in... Closed

 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.
Maintenance periods can be very convenient in two situations :
1) you can use a maintenance period to fit the unavalability time of your service (during the night for instance), instead of hard coding that in the triggers. It is very much more flexible to use Maintenance periods (without data collection, of course) because you can just drag and drop hosts/hosts groups into or out of the maintnance. Careful however with functions in trigger expressions because they have a tendancy to behaving strangely when the maintenance period ends.
Someting else : if a trigger is raised just before the start of the daily maintenance period, the trigger will stay ON (Problem) during the whole maintenance period and alerts will be snt and escalation steps will increment. The trigger will switch back to normal only when the maintenance period finishes.
2) in case of an event, you might want to setup/enable a maintenance period for the hosts or host group (or add the host to a pre-defined maintenance period) so that you have time to fix the issue on your service with having zabbix spam with e-mail alerts. Right now, that doesn't work because during maintenance, the action condition isn't evaluated. That's a shame.

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.
I don't recall exactly how long you have to disable the host, but I'm pretty sure it has to be at least as long as the step duration.... Unfortunately, I don't have time to verify this now.

@Zabbix : apparently, we aren't the only ones to require this to be fixed. Any idea when that is planned ?
Thanks.

Comment by Oleksii Zagorskyi [ 2016 Feb 20 ]

Issue summary in other words, IMO:
Add condition "Host maintenance status" to supported conditions for operations.

Would you agree to update the summary ?

Comment by Aleksandrs Saveljevs [ 2016 Feb 22 ]

Adding maintenance status condition for operations is requested in ZBXNEXT-128.

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 ZBXNEXT-128

Comment by itcbsops [ 2016 Feb 22 ]

Aleksandrs ,

Got your point. Thanks

Comment by Oleksii Zagorskyi [ 2016 Feb 22 ]

Closing as duplicate.

Generated at Thu Apr 25 17:43:55 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.