All,
For my first post here on the forum, I'd like to pose this problem ...
The logic testing of a trigger expression using the time(0) function is not correct.
Using Zabbix 1.8.3 on Linux (CentOS 5.5, PgSQL 8.4.x)
I'm actually using a trigger like on the manual,
{HOST1:agent.ping.nodata(300)}=1 & {HOST1:agent.ping.time()}>000000 & {HOST1:agent.ping.time()}<060000
This logic should trigger only between 00:00 and 06:00 hours when the agent on HOST1 is not sending pings for 5 minutes.
In the 'test' when I put in 094500 as the time(0),
The TRUE is at the <060000 statement and not at the >000000 as it should be.
While the range 000001 till 055959 triggers an all TRUE correctly, it is very counter intuitive to have the >000000 display a FALSE and the <060000 displaying a TRUE.
(currently unable post pictures though, but my guess is, its easily replicated)
What I'm actually trying to build is a trigger with 4 time schedules built in, but if I'm unable to test the logic correctly, I'm unsure if the problem is in the logic tester, or in the trigger engine .....
If the problem is in the tester only, the trigger might work correctly......
Anybody have an idea ?
For my first post here on the forum, I'd like to pose this problem ...
The logic testing of a trigger expression using the time(0) function is not correct.
Using Zabbix 1.8.3 on Linux (CentOS 5.5, PgSQL 8.4.x)
I'm actually using a trigger like on the manual,
{HOST1:agent.ping.nodata(300)}=1 & {HOST1:agent.ping.time()}>000000 & {HOST1:agent.ping.time()}<060000
This logic should trigger only between 00:00 and 06:00 hours when the agent on HOST1 is not sending pings for 5 minutes.
In the 'test' when I put in 094500 as the time(0),
The TRUE is at the <060000 statement and not at the >000000 as it should be.
While the range 000001 till 055959 triggers an all TRUE correctly, it is very counter intuitive to have the >000000 display a FALSE and the <060000 displaying a TRUE.
(currently unable post pictures though, but my guess is, its easily replicated)
What I'm actually trying to build is a trigger with 4 time schedules built in, but if I'm unable to test the logic correctly, I'm unsure if the problem is in the logic tester, or in the trigger engine .....
If the problem is in the tester only, the trigger might work correctly......
Anybody have an idea ?
Comment