Ad Widget

Collapse

ICMP Ping = 0 for 60 minutes => Trigger

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • c1support
    Member
    • Apr 2020
    • 47

    #1

    ICMP Ping = 0 for 60 minutes => Trigger

    Hi there
    I am still new to Zabbix (great tool btw), and I am still a bit struggling with syntax.
    What I would like to do is generating a trigger when a host is unresponsive for a loger period of time.

    Zabbix Server 4.4.7
    Target system has no client; SSH access is not allowed

    I have been successfully using "Template Module ICMP Ping" with the syntax
    Code:
    {targetSystem:icmpping.max(#3)}=0
    This generates a trigger after three unsuccessful pings with severity "High").

    Now, I would like to do more less the same, but only generating a trigger after the target system has been unresponsive for say 60 minutes.
    I imagine something like
    Code:
    {targetSystem:icmpping.max(#3).average(60m)}=0
    However, this raises the error "Cannot add trigger: incorrect trigger expresseion" (which I kind of expected).

    After some bad experiences with Zabbix Scripts where I forgot to limit the number of pings, I am a bit hesitant trying
    Code:
    {targetSystem:icmpping.avg(60m)}=0
    {targetSystem:icmpping.count(60m)}=0
    => Is this even possible with simple checks (https://www.zabbix.com/documentation.../simple_checks)?
    => If not, would it be possible to use Actions and Escalation (https://www.zabbix.com/documentation...on/escalations)?
    => Or is there a better suited concept?

    Note: in the end of the day, it is important that the result is a normal trigger (because I do some alarming using Zabbix API, which in turn relies upon triggers).
  • Semiadmin
    Senior Member
    • Oct 2014
    • 1625

    #2

    {targetSystem:icmpping.max(60m)}=0
    but {targetSystem:icmpping.avg(60m)}=0 is the same
    or {targetSystem:icmpping.count(60m,1)}=0

    Comment

    • c1support
      Member
      • Apr 2020
      • 47

      #3
      Thank you very much for the fast reply!
      Seems to work with shorter durations (I only tried "max(4m)"), currently testing "max(60m)".

      Comment

      Working...