Ad Widget

Collapse

Count number of hosts not reachable in group

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ad@kbc-clearing.com
    Member
    • Sep 2005
    • 77

    #16
    Sorry, I have never reported an issue before. I am a happy Zabbix user.

    I just created an account in support.zabbix.com, but I have no clue how to make an issue in this ......

    Comment

    • walterheck
      Senior Member
      • Jul 2009
      • 153

      #17
      After you log in, go here and look for the "Create issue" link in the top right hand corner: https://support.zabbix.com/browse/ZBX
      Free and Open Source Zabbix Templates Repository | Hosted Zabbix @ Tribily (http://tribily.com)

      Comment

      • ad@kbc-clearing.com
        Member
        • Sep 2005
        • 77

        #18
        I logged an issue zbx-2980.
        It has been declined (won't fix), stating that the field agent.ping should be userd instead.
        But I disagree with that: agent.ping and status have different functionality in case a host is not reachable.

        Comment

        • ad@kbc-clearing.com
          Member
          • Sep 2005
          • 77

          #19
          The field status will not be supported anymore in 2.0.
          I have a workaround to reach my goal.
          I made a calculated item agent.status wtith formula nodata(agent.ping,120).
          This item will be 1 when the agent on a host could not be reached during 120 secs. Now I can use grpsum to count the number of not reachable hosts, and make a trigger if this grpsum exceeds a certain threshold.

          Thanks to Aleksandrs Saveljevs !

          Comment

          Working...