Ad Widget

Collapse

when zbbix-proxy is down,the triggers “ Zabbix agent is not available” don‘t work

Collapse
This topic has been answered.
X
X
 
  • Time
  • Show
Clear All
new posts
  • lhb6540
    Junior Member
    • Jul 2022
    • 5

    #1

    when zbbix-proxy is down,the triggers “ Zabbix agent is not available” don‘t work

    when zbbix-proxy is down,the triggers “ Zabbix agent is not available” of all hosts monitored by proxy don‘t work.
    but if the zabbix-proxy is work normally,only the zabbix-agent of the hosts monitored by proxy down, the trigger “ Zabbix agent is not available” work normally.
    Is the logic of the trigger designed like this? or is it a bug?
    This phenomenon can be reproduced on zabbix 5.0 LTS and 6.0 LTS
  • Answer selected by lhb6540 at 18-08-2022, 07:43.
    cyber
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2006
    • 4807


    nodata .... "Since Zabbix 5.0, the 'nodata' triggers monitored by proxy are, by default, sensitive to proxy availability - if proxy becomes unavailable, the 'nodata' triggers will not fire immediately after a restored connection, but will skip the data for the delayed period. Note that for passive proxies suppression is activated if connection is restored more than 15 seconds and no less than 2 & ProxyUpdateFrequency seconds later. For active proxies suppression is activated if connection is restored more than 15 seconds later.

    To turn off sensitiveness to proxy availability, use the second parameter, e.g.: nodata(5m,strict); in this case the function will work the same as before 5.0.0 and fire as soon as the evaluation period (five minutes) without data has past."

    Comment

    • cyber
      Senior Member
      Zabbix Certified SpecialistZabbix Certified Professional
      • Dec 2006
      • 4807

      #2

      nodata .... "Since Zabbix 5.0, the 'nodata' triggers monitored by proxy are, by default, sensitive to proxy availability - if proxy becomes unavailable, the 'nodata' triggers will not fire immediately after a restored connection, but will skip the data for the delayed period. Note that for passive proxies suppression is activated if connection is restored more than 15 seconds and no less than 2 & ProxyUpdateFrequency seconds later. For active proxies suppression is activated if connection is restored more than 15 seconds later.

      To turn off sensitiveness to proxy availability, use the second parameter, e.g.: nodata(5m,strict); in this case the function will work the same as before 5.0.0 and fire as soon as the evaluation period (five minutes) without data has past."

      Comment

      • lhb6540
        Junior Member
        • Jul 2022
        • 5

        #3
        Originally posted by cyber
        https://www.zabbix.com/documentation...gers/functions
        nodata .... "Since Zabbix 5.0, the 'nodata' triggers monitored by proxy are, by default, sensitive to proxy availability - if proxy becomes unavailable, the 'nodata' triggers will not fire immediately after a restored connection, but will skip the data for the delayed period. Note that for passive proxies suppression is activated if connection is restored more than 15 seconds and no less than 2 & ProxyUpdateFrequency seconds later. For active proxies suppression is activated if connection is restored more than 15 seconds later.

        To turn off sensitiveness to proxy availability, use the second parameter, e.g.: nodata(5m,strict); in this case the function will work the same as before 5.0.0 and fire as soon as the evaluation period (five minutes) without data has past."
        Thanks a lot,now the problem is sloved

        Comment

        Working...