Ad Widget

Collapse

Trigger host unreachable for 10 minutes straight

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • obrienmd
    Junior Member
    • Jul 2010
    • 26

    #1

    Trigger host unreachable for 10 minutes straight

    I've been reading through this thread: http://www.zabbix.com/forum/archive/index.php/t-75.html

    And all information still seems applicable, as the lines:
    {host:status.min(600)}=2
    {host:status.avg(600)}=2

    Still trigger after a single unreachable instance, as the avg/min functions are running on a bunch of "nodata" null entries and the single "2" entry. Is there a way around this with a modern version of Zabbix (we're on 1.8)?

    Thanks in advance!
  • fascinatedcow
    Junior Member
    • Mar 2010
    • 20

    #2
    use agent.ping.nodata(600)

    Comment

    • obrienmd
      Junior Member
      • Jul 2010
      • 26

      #3
      Hrm...

      I feel like an idiot, but exactly how would I use that variable in this trigger? Maybe it's because I'm not looking at my config right now, but what formula would you use exactly?

      Comment

      • fascinatedcow
        Junior Member
        • Mar 2010
        • 20

        #4
        Make sure you have an item with type "Zabbix Agent" and key "agent.ping". Then your trigger will look something like this:

        Code:
        {Template_Linux:agent.ping.nodata(600)}
        In our case the "host" is actually a template called "Template_Linux", which contains the item mentioned above. The 600 is the number of seconds for which no data has been collected for that item, i.e. agent pings have been failing.

        Does that makes sense?

        Comment

        Working...