-
Incident report
-
Resolution: Duplicate
-
Critical
-
None
-
None
-
None
There seems to be a discrepancy between the eventid and the event timestamp. For example:
{ "eventid": "78933", "source": "0", "object": "0", "objectid": "13491", "clock": "1448541423", "value": "0", "acknowledged": "0", "ns": "200237451" }, { "eventid": "78932", "source": "0", "object": "0", "objectid": "13491", "clock": "1448541425", "value": "1", "acknowledged": "0", "ns": "199083444" }
The value of the trigger is "0" (thus I am guessing is decided by latest eventid). Is this a known bug? I am using Zabbix 2.4
- duplicates
-
ZBX-8556 Events page shows wrong duration in case of nodata() trigger and delayed data
- Open