Hi, this is my first post here but I've been using Zabbix for some time.
We have a 4.0.0 server and Active Windows Agents running 4.0.6 with SSL.
What I'm noticing is that when an agent's time is changed drastically (for example I set the year to 2020) the information that is captured in the Zabbix front-end is put into the time that is set on the Agent rather than the time on the server.
For example; Once I set the year to 2020 on the Windows machine, I have to look at today's date next year under latest data to see the most recent values.
Is this normal behavior? I'm ok if this is how the information is stored but I can't seem to setup a trigger that can capture when the time goes out of sync on of our agents.
I have this item: "system.localtime" as a Numeric(Float) value with an interval of 1m.
Then I have this trigger: "{Example Agent:system.localtime.fuzzytime(300)}=0".
The goal is simply to know if the time is off by 5 or more minutes. Ideally I'd like to get more precise than this but I would be happy with 5 minutes but this is not working.
We have a 4.0.0 server and Active Windows Agents running 4.0.6 with SSL.
What I'm noticing is that when an agent's time is changed drastically (for example I set the year to 2020) the information that is captured in the Zabbix front-end is put into the time that is set on the Agent rather than the time on the server.
For example; Once I set the year to 2020 on the Windows machine, I have to look at today's date next year under latest data to see the most recent values.
Is this normal behavior? I'm ok if this is how the information is stored but I can't seem to setup a trigger that can capture when the time goes out of sync on of our agents.
I have this item: "system.localtime" as a Numeric(Float) value with an interval of 1m.
Then I have this trigger: "{Example Agent:system.localtime.fuzzytime(300)}=0".
The goal is simply to know if the time is off by 5 or more minutes. Ideally I'd like to get more precise than this but I would be happy with 5 minutes but this is not working.
Comment