Hysteresis for proxy last access

[Andreas Bollhalder]

Hello

I have a trigger with hysteresis for the Proxy last access like this:
UPDATE: it does not work

({HOST:zabbix[proxy,"PROXY",lastaccess].fuzzytime(90)}=0)
|
(
({TRIGGER.VALUE}=1)
&
(6*{HOST:icmpping.now(0)}-{HOST:zabbix[proxy,"PROXY",lastaccess].sum(6)}>480)
)

The proxy last access is written every 30s and if the connection to the proxy goes down, the last time is written still every 30s. With this, the trigger should stay as long as the last 5 values (n-1) aren't incremented.

Is it possible to simplify the expression "{HOST:icmpping.now(0)}" ? How are you doing a trigger for that ?

I need a hysteresis to avoid unneeded alerts for triggers with nodata or based on values in a time range. The value 480 came from "0+30+60+90+120+150" which is 450 and added a 30s for security. If you change the value 6 for the multiplicator of "now()" and "sum()", than you have to shrink or extend the progression at the end. If you have another proxy frequency, then use that value in the progression.

I believe, a trigger like this should be of interest for all proxied monitoring setups. So, share your thoughts.

Andreas

[Andreas Bollhalder]

Now, I will see, if this one does, what I want. It uses only the lastaccess values of the proxy and doesn't use special functions like now() or fuzzytime().

({x.delta(#5)}=0)
|
(
  ({TRIGGER.VALUE}=1)
  &
  (
    ({x.avg(#6)}-{x.last(#6)}-75>2)
    |
    ({x.avg(#6)}-{x.last(#6)}-75<-2)
  )
)

Replace "x" with "<ZBXSVR>:zabbix[proxy,"<ZBXPRX>",lastaccess]". This example depends on the lastaccess updated around every 30s. Default is 60s in the proxy configuration. There is a window of +-2s, because sometimes the DB is updated after 29s or 31s... The value 75 is the half of the time difference from the first to the last checked value over 6 values with 30s steps.

The description of the trigger could be:

Zabbix proxy <ZBXPRX> has not delivered consecutive data for >90s (OK after >150s consecutive data)

Andreas