Loading...

XML

Word

Printable

Type: New Feature Request
Resolution: Fixed
Priority: Major
Fix Version/s: 3.2.0alpha1
Affects Version/s: None
Component/s: API (A), Frontend (F), Server (S)
Labels:

Current processing of maintenance periods produces new events at the end of maintenance that confuses Zabbix users. It's hard to understand who generated these events and why, information about acknowledgment of the original event is lost as well.

We should pause escalation during maintenance periods instead.

duplicates

ZBX-8558 Wrong event is generated at an end of maintenance period - nodata() trigger and delayed data

Closed

is duplicated by

ZBX-10265 Generating duplicated events after maintenance even when trigger didn't change state during real maintenance period

Closed

Assignee:: Unassigned

Reporter:: Alexander Vladishev

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Created:: 2016 Mar 17 09:22

Updated:: 2019 Feb 21 15:49

Resolved:: 2016 Jun 06 22:16

Details

Description

Attachments

Issue Links

Activity

People

Dates