-
Problem report
-
Resolution: Fixed
-
Major
-
5.0.9
-
Windows 10 / Zabbix Agent2
-
Sprint 75 (Apr 2021), Sprint 76 (May 2021)
-
0.5
Eventlog or Log monitoring
Agent2 in Windows - Nanoseconds would be stored in the data with the same value.
history: insert into history_log (itemid,clock,ns,timestamp,source,severity,value,logeventid) values (32642,1617165992,23678700,0,'',0,'test1',0); insert into history_log (itemid,clock,ns,timestamp,source,severity,value,logeventid) values (32642,1617165992,23678700,0,'',0,'test2',0); insert into history_log (itemid,clock,ns,timestamp,source,severity,value,logeventid) values (32642,1617165992,23678700,0,'',0,'test3',0); ...
{ITEM.VALUE} macro does not correct the log value that was generated due to same ns value
events: TEST item.value! - test3 TEST item.value! - test3 TEST item.value! - test3
Confirmed with Agent2/Windows.
This does not occur in Agent 5.0/Windows or Agent2/RHEL7 (ns value is different).