Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  2. ZBX-6174

Triggers not displayed in the dashboard when dependent triggers exist but are in disabled state


    • Icon: Incident report Incident report
    • Resolution: Fixed
    • Icon: Trivial Trivial
    • 2.0.14rc1, 2.2.7rc1, 2.4.1rc2, 2.5.0
    • 2.0.4
    • Frontend (F)

      I spent a lot of time trying to debug the following issue:

      Suddenly we stopped receiving alerts in the dashboard for hosts in certain subnet (also in a separate Zabbix group, monitored by separate Zabbix proxy). The email notifications worked, though.
      Initially I suspected that this was an issue on the proxy, even went so far as to recreate that proxy's DB. No luck. Spent half a day digging thru (other) performance problems with Zabbix, still looking for the mysterious bug. No luck again.
      We've thought at the time the bug was affecting every trigger on the host, and couldn't find it.

      At the end of a day I discovered by chance that the gateway for this host stopped responding to ICMP pings awhile ago, then I had a theory... It turned out that all of our hosts had a trigger for this host being unreachable, with expression like 'agent.ping.nodata(300). Also that trigger was dependent on a trigger for that hosts's gateway being unreachable. Strangely, when I had this linked to the "Host unreachable" trigger, the alerts for unreachable hosts stopped popping up on the dashboard if the gateway for this host didn't respond to ICMP pings, even if the "gateway unreachable" trigger itself was disabled.
      But what's more strange, we kept receiving email alerts for those unreachable hosts.

            Unassigned Unassigned
            ygorshkov Yuri Gorshkov
            1 Vote for this issue
            5 Start watching this issue