[ZBX-19083] false positives of a trigger with nodata() Created: 2021 Mar 04  Updated: 2021 Mar 08  Resolved: 2021 Mar 08

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 5.0.8
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Aliaksei Halouka Assignee: Igor Gorbach (Inactive)
Resolution: Won't fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2021-03-04-13-39-52-773.png     PNG File image-2021-03-04-13-41-45-476.png     PNG File image-2021-03-04-13-43-42-065.png     PNG File image-2021-03-04-13-48-40-540.png    

 Description   

Steps to reproduce:

  1. There are several triggers with nodata(24h)}=0 on different hosts, and it is already in the triggered state, as there is really no data in the data item for that time. At some point, on zabbix proxy, pollers utilization goes from 10 to 100% (this is something I have yet to figure out, but it brings up the following problem)
  2. Further, it is seen that due to accumulated data, the utilization of the sender process on the zabbix proxy grows to 100%. This of course causes maximum load of trapers on the zabbix server, the server is unable to process the data stream, this can be seen by the intermittent graph from any item.
  3. After this chain, triggers with nodata start to go crazy. Trigger with condition nodata(24h) or any other time, lights up and goes out every 30 seconds. If you review the history by element, there was no data at that time.

Result:

 

 Comments   
Comment by Igor Gorbach (Inactive) [ 2021 Mar 08 ]

Hello!
In case, when data cannot to be written into history (overload), then condition
nodata(24h) is false - because nodata function has calculating every 30 seconds and if we have short gap - trigger has firing and resolving any time when we have a gap and when it will be restored
Another question - why Zabbix can't get in time write the history - but it looks like a problem with hardware or missconfigurataion, but not a bug

Comment by Aliaksei Halouka [ 2021 Mar 08 ]

I still do not understand why nodata (24h) is false at the gap, because it is the same lack of data as with a non-working item.

Generated at Sat May 03 07:07:32 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.