[ZBX-15920] Nodata trigger is "fired" after maintenance ends (Zabbix 4.0) Created: 2019 Apr 02  Updated: 2019 Oct 09  Resolved: 2019 Apr 09

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 4.0.6
Fix Version/s: 4.0.7rc1, 4.2.1rc1, 4.4.0alpha1, 4.4 (plan)

Type: Problem report Priority: Major
Reporter: Kim Jongkwon Assignee: Andris Zeila
Resolution: Fixed Votes: 1
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 01_maintenance.png     PNG File 02_maintenance_period.png     PNG File 03_events.png    
Issue Links:
Duplicate
is duplicated by ZBX-15838 Spam message via all media after main... Closed
is duplicated by ZBX-15939 Zabbix agent on <servername> is unrea... Closed
Team: Team A
Sprint: Sprint 51 (Apr 2019)
Story Points: 1

 Description   

ZBX-6294 fixed but a similar problem happened again in 4.0

Nodata function behavior is not correspond with documentation: https://www.zabbix.com/documentation/4.0/manual/maintenance

When “no data” maintenance ends, triggers using nodata() function will not fire before the next check during the period they are checking.

If using Default "Template App Zabbix Server" with “no data” maintenance 10 min.
I confirmed all fire "Zabbix agent on Zabbix server is unreachable for 5 minutes" trigger. (agent.ping and nodata(5m)=1)

Look screenshots for getting more information.



 Comments   
Comment by Ingus Vilnis [ 2019 Apr 02 ]

Duplicate of ZBX-15838

Generated at Fri Mar 29 11:24:48 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.