-
Change Request
-
Resolution: Duplicate
-
Major
-
None
-
1.8.15
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.
- duplicates
-
ZBXNEXT-128 New condition for operations: host is not in maintenance
- Closed