[ZBXNEXT-6621] Log timestamp issue retrieved by Zabbix Agent Created: 2021 Mar 22  Updated: 2021 Apr 15

Status: Reopened
Project: ZABBIX FEATURE REQUESTS
Component/s: Agent (G), Server (S)
Affects Version/s: 5.0.9
Fix Version/s: None

Type: New Feature Request Priority: Trivial
Reporter: Yasumi Assignee: Zabbix Support Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The time stamp when the log acquired by Zabbix agent is stored in the "HISTORY" is not the time stamp on the Zabbix server side, but the time stamp when it is sent from Zabbix agent.

However, this specification has major problems.

For security reasons, intentionally disconnect the monitored host from the network and restore communication after resolution. Then, the time stamp of the log stored in "HISTORY" of Zabbix server will be the time (past) at the time of occurrence instead of the present. As a result, it is not possible to know when the log was stored in "HISTORY" of Zabbix server.

Also, the event displayed in "Problems" suddenly appears to have been inserted in the past rather than the occurrence of the current time. There was no description of this specification in the reference, which caused a great deal of confusion when investigating the failure.

Since it is divided into "Timestamp" and "Local time", can we change the specifications so that the display of "Timestamp" is the time on the Zabbix server side?



 Comments   
Comment by Edgars Melveris [ 2021 Apr 01 ]

This is actually working as expected, because by design we want to have the timestamp of the event, not the timestamp of when it was stored in the server DB, as that could be much later than the event because of multiple reasons.

I'm closing this as not a bug.

Comment by Yasumi [ 2021 Apr 02 ]

Thanks Edgars Melveris.

Thank you for your reply.
Sure, it works as expected, but I'm hoping for a spec that adds the time stamp when the log was stored in the server DB.

Comment by Edgars Melveris [ 2021 Apr 15 ]

In that case this should have been feature request. I'll move it to that project.

Generated at Sat Apr 04 09:41:15 EEST 2026 using Jira 10.3.13#10030013-sha1:56dd970ae30ebfeda3a697d25be1f6388b68a422.