[ZBX-19208] Log data has the same clock and ns (Agent2 - Windows) Created: 2021 Apr 05  Updated: 2024 Apr 10  Resolved: 2021 May 31

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 5.0.9
Fix Version/s: 5.0.13rc1, 5.2.7rc1, 5.4.1rc1, 6.0.0alpha1, 6.0 (plan)

Type: Problem report Priority: Major
Reporter: Kim Jongkwon Assignee: Dmitrijs Goloscapovs
Resolution: Fixed Votes: 0
Labels: Agent2, eventlog, log, windows
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 10 / Zabbix Agent2

Issue Links:
Duplicate
Team: Team A
Sprint: Sprint 75 (Apr 2021), Sprint 76 (May 2021)
Story Points: 0.5

 Description   

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).

 Comments   
Comment by Dmitrijs Goloscapovs [ 2021 May 28 ]

Available in versions:

Generated at Sat Apr 19 02:28:53 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.