Ad Widget

Collapse

HTTP trigger not working on new zabbix

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Celestin
    Junior Member
    • Sep 2013
    • 3

    #1

    HTTP trigger not working on new zabbix

    Hi,

    Recently we upgraded from 1.8 Zabbix to 2.0. On old one we had trigger which would notify us if httpd service went down.

    This was the trigger that worked fine on old zabbix

    {http_test:net.tcp.service[http,,80].last(0)}=0
    On new 2.0 zabbix it's giving allot of false alarms.

    We also tried with thise
    {http_test:net.tcp.service[http,,80].last(#3)}=0
    {http_test:net.tcp.service[http,,80].count(#3)}<1
    But none of this give us desired result, either they do not function at all or they give allot of false alerts.

    Anyon knows how to build a trigger on zabbix 2.0 to notify us if httpd is down for, let say, 20 seconds ?
  • angelhc
    Senior Member
    Zabbix Certified Specialist
    • Nov 2009
    • 226

    #2
    From the documentation:


    You can take a look to this example:

    {zabbix.zabbix.com:icmpping.count(1800,0)}>5

    The expression is true if host “zabbix.zabbix.com” is unreachable more than 5 times in the last 30 minutes.

    And taylor it to fit your needs.
    Number of hosts 1600,Number of items +90k,Number of triggers +22k, Number of users +100, New values per second +1270

    http://zabbixes.wordpress.com/

    Comment

    • Celestin
      Junior Member
      • Sep 2013
      • 3

      #3
      It seems it's working, for now at least. Thank you

      Comment

      Working...