-
Problem report
-
Resolution: Fixed
-
Trivial
-
5.0.16
-
None
-
Zabbix Server 5.0
-
Sprint 84 (Jan 2022), Sprint 85 (Feb 2022), Sprint 86 (Mar 2022), Sprint 87 (Apr 2022), Sprint 88 (May 2022), Sprint 89 (Jun 2022), Sprint 90 (Jul 2022), Sprint 91 (Aug 2022), Sprint 92 (Sep 2022), Sprint 93 (Oct 2022), Sprint 94 (Nov 2022), Sprint 95 (Dec 2022), Sprint 96 (Jan 2023), Sprint 97 (Feb 2023), Sprint 98 (Mar 2023), Sprint 99 (Apr 2023), Sprint 100 (May 2023), Sprint 101 (Jun 2023), Sprint 102 (Jul 2023)
-
2
Case1
If there is no event to be deleted in the first housekeeper after (re)starting Zabbix server, the event will not be deleted until "the housekeeper exection time(A) + Trigger data storage period" has elapsed.
Case2
If there is an events to be deleted in the first housekeeper after (re)starting Zabbix server, the event will not be deleted until "the time of the event(B) + Trigger data storage period" has elapsed.
If an event older than the time (A) or (B) is subsequently closed, the event will not be deleted after the Trigger data storage period.
In an environment where old events continue to remain, such as an environment with a lot of log monitoring, a large number ofo events may remain without being deleted.
