Ad Widget

Collapse

Debugging a trigger/alarm

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jkreiger9924
    Junior Member
    • Feb 2015
    • 2

    #1

    Debugging a trigger/alarm

    I'm trying to monitor my name servers by sending a query for root. similar to:
    dig @server . NS

    I set up an External check item that simply returns each nsdname found in the answer section of the DNS packet.
    I've set the Type of information to Text.

    Inventory -> Latest Data -> History shows me the response I expect (with one server per line)

    But my trigger is alarming. I've tried lots of triggers, but they all fail
    {External UDP.DNS Check:dnsc.pl["-h","{HOST.CONN}","-n",".","-r","NS"].str("root-servers.net")}=1
    {External UDP.DNS Check:dnsc.pl["-h","{HOST.CONN}","-n",".","-r","NS"].str("net")}=1
    {External UDP.DNS Check:dnsc.pl["-h","{HOST.CONN}","-n",".","-r","NS"].regex("[a-z].root-servers\.net")}=1

    Can someone explain what is going wrong or how I find out what's confused ?

    FYI: my dnsc.pl is available at http://pastebin.com/raw.php?i=Fu83kD4s
  • jkreiger9924
    Junior Member
    • Feb 2015
    • 2

    #2
    Originally posted by jkreiger9924
    I'm trying to monitor my name servers by
    Can someone explain what is going wrong or how I find out what's confused ?
    Thanks to Jan on zabbix-users, this has been cleared up.

    I thought the trigger expression was "When are things okay" and not "When should we alarm". Changing the =1 at the end of the expressions to #1 fixed it right up.

    Comment

    Working...