-
Incident report
-
Resolution: Duplicate
-
Major
-
None
-
2.2.11, 2.4.7, 3.0.0alpha6
Steps for reproduce:
- make trigger in PROBLEM state
- acknowledge it
- put host in active maintenance
- make sure that timer mark host under maintenance
- put out host from maintenance
You see that was generated new event and trigger become unacknowledged, it is unexpected behavior for setups where acknowledging used as indication that problem is known and somebody work on it.
- duplicates
-
ZBXNEXT-3196 New option for actions: delay escalation while in maintenance
- Closed