-
Incident report
-
Resolution: Duplicate
-
Major
-
None
-
2.4.5
-
None
Hi guys,
I believe I've discovered a bug. No sure if this is coming from the sender, the agent, or the server itself.
We have a script that returns:
hostname, key, timestamp, value. Here is part of that output
sprintlab474vm30 EtloadCountersCount_nokbsc 1437530400 42291608
sprintlab474vm30 EtloadCountersCount_nokmww 1437530400 61476448
sprintlab474vm30 EtloadCountersCount_pcosgn 1437534000 58441648
sprintlab474vm30 EtloadCountersCount_nokbsc 1437534000 58300755
sprintlab474vm30 EtloadCountersCount_pcofng 1437534000 23244000
sprintlab474vm30 EtloadCountersCount_nokmww 1437534000 61279219
sprintlab474vm30 EtloadCountersCount_xmlnss 1437534000 52044507
sprintlab474vm30 EtloadCountersCount_pcofng 1437537600 23244000
sprintlab474vm30 EtloadCountersCount_nokmww 1437537600 61807208
sprintlab474vm30 EtloadCountersCount_pcosgn 1437537600 58441648
sprintlab474vm30 EtloadCountersCount_xmlnss 1437537600 53001600
sprintlab474vm30 EtloadCountersCount_nokbsc 1437537600 42743715
sprintlab474vm30 EtloadCountersCount_nokmww 1437541200 61213970
Notice that the timestamps are Hourly.
So, they correspond to 10am of today, 11am, etc.
After running the sender on top of this file, using MySQL, or even zabbix UI to see the latest data, I can see that sometime he writes 1sec before.
So for example, the 11:00:00 timestamp, would be written with 10:59:59 timestamp.
That's a big problem for us because that means that this data would belong to 10-11 period.
Can you confirm this bug?
- duplicates
-
ZBX-8730 Values sent with timestamp over zabbix-sender have incorrect time on zabbix server
- Closed