Zabbix monitoring alarm system time does not take effect

[Nathan]

Use the default key value monitoring: [system.localtime], you can get the time information of the agent. After deliberately set to the wrong time, the trigger should give an alarm, but no prompt information appears. All configurations are adopted The system default configuration items, what should I do? Please see the attachment for detailed configuration
ServerVersion: 5.0.2
AgentdVersion: 5.0.2
Thank you

[dimir]

FYI, since 4.0 monitoring time difference using active agent became useless because server/proxy stopped adjusting (received packet timestamp vs server time) value timestamps coming from the agent. The reason mainly, this was giving more negative effect than positive. So we decided to stop doing that and strongly advise users to use NTP, plus, for fuzzytime always use passive checks.

Here's the related ticket: https://support.zabbix.com/browse/ZB...comment-317852
Sections where this change was documented: https://support.zabbix.com/browse/ZB...comment-328764

[Nathan]

thank you for your reply!
I saw your discussion. The version I am currently using is 5.0.2. For some reasons, I can only monitor the host in active mode, mainly for the following reasons:
1. Some hosts exist in the internal network environment and cannot directly connect to the external network
2. The ntp server may also be unreliable or downtime
3.zabbix cannot warn after ntp error
4. Very strict port restrictions on the host, only active mode
5. At the same time, I found a very important problem: currently when the host time is modified to an earlier time, zabbix will stop updating any monitoring items under the host, which is very dangerous for the host. Because our programs are very dependent on the system, if the entire host is down, zabbix will not generate new alarms
For the above reasons, I am very eager to realize that system.localtime can work normally in active mode in the current or latest version. I want to confirm whether you currently have an update or repair plan related to this project. Zabbix is very powerful, but if this fatal flaw cannot be fixed, I will not be able to continue to use zabbix as the main monitoring service in the production environment. Looking forward to your reply, thank you very much