-
Incident report
-
Resolution: Duplicate
-
Major
-
None
-
2.2.7
-
None
-
Ubuntu Vivid Linux
When Zabbix receives external events and there is a trigger like
{hostname:somedata.nodata(300)}sometimes trigger will have wrong status and stay in it. Consequence: dashboard shows trigger in state error while in reality it is not.
This might be related to processing of burst of messages via trapper, but that is not proven. The burst occurs, when trapper data network stream was stalled due to network errors. After network errors a burst of timestamp sorted messages is inserted, but some may have timestamps dating back more than the nodata(timeout) value.
- duplicates
-
ZBX-9432 Multiple consecutive events the same type (OK or PROBLEM)
- Open