-
Type:
Incident report
-
Resolution: Won't fix
-
Priority:
Major
-
None
-
Affects Version/s: 1.8.3
-
Component/s: Server (S)
-
Environment:Debian Lenny with zabbix-server-pgsql from backports ( version 1.8.2 )
I have defined a trigger for a host
{quimerix-test:room.temperature.last(0)}>35
And I am filling data to the server with zabbix_sender using timestamps for each event.
I want to simulate an environment where my agent don't send the data in real-time. It saves the data on a file and sends it to the server once a day for example.
The event triggers when "room.temperature.last >35"
If I send room.temperature = 32 with an arbitrary timestamp
$ echo quimerix-test room.temperature $(date --date "Jan 12 15:15:15 2011" +%s) 36 | zabbix_sender -z zabbix-server -T -i -
And then I send room.temperature = 40 with a timestamp in the past respect the previous one:
$ echo quimerix-test room.temperature $(date --date "Jan 12 12:12:12 2011" +%s) 36 | zabbix_sender -z zabbix-server -T -i -
The events gets triggered and it should not be the case, because the value with the newer timestamp is 32 despite the fact that 40 was received later.
In summary: triger.last should take the "timestamp" value of the data and ignore when it was received.