Ad Widget

Collapse

Latency Trigger expression and false fire

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • g1zm0e
    Junior Member
    • Jul 2014
    • 3

    #1

    Latency Trigger expression and false fire

    I have to following trigger setup

    {PINGTEMP:icmppingsec.max(300)}>150

    I also tried the max(#5)}>150

    What I want it to do is if the response time is OVER 150 Msec consistently, during that 5 min window, to trigger. However, it seems to trigger even if one response is over the 500msec timeframe. I tried to use average, however, that did not work well.

    Can anyone give some assitance?
  • BDiE8VNy
    Senior Member
    • Apr 2010
    • 680

    #2
    Fires when all probes/values within 5 minutes are grater than 150
    Code:
    {PINGTEMP:icmppingsec.min(5m)}>150

    Comment

    • g1zm0e
      Junior Member
      • Jul 2014
      • 3

      #3
      Originally posted by BDiE8VNy
      Fires when all probes/values within 5 minutes are grater than 150
      Code:
      {PINGTEMP:icmppingsec.min(5m)}>150
      Just because I fell like an idiot, can you explain the difference between MAX, MIN, and Count? I was under the impression that MIN was 1 value matches within that 5 mins and it fires, where max would fire only if all of them matched?

      Right now I have a count(#5)>150 test trigger also, would this work?

      thank you so much

      Comment

      • coreychristian
        Senior Member
        Zabbix Certified Specialist
        • Jun 2012
        • 159

        #4
        Originally posted by g1zm0e
        Just because I fell like an idiot, can you explain the difference between MAX, MIN, and Count? I was under the impression that MIN was 1 value matches within that 5 mins and it fires, where max would fire only if all of them matched?

        Right now I have a count(#5)>150 test trigger also, would this work?

        thank you so much
        It really depends a little if you are doing greater then or less then in your expression.

        I believe this is how it works.

        MIN/MAX(#5)>150 = If the minimum/maximum value over the past 5 data points is greater then 150 trigger
        MIN/MAX(#5)<150 = If the minimum/maximum value over the past 5 data points is less then 150 trigger

        Count is the combined total of the values for the past XYZ time period.

        It can take a little playing around with though, and if you haven't seen it there are pretty good definitions and examples in the docs.

        Comment

        • g1zm0e
          Junior Member
          • Jul 2014
          • 3

          #5
          Originally posted by coreychristian
          It really depends a little if you are doing greater then or less then in your expression.

          I believe this is how it works.

          MIN/MAX(#5)>150 = If the minimum/maximum value over the past 5 data points is greater then 150 trigger
          MIN/MAX(#5)<150 = If the minimum/maximum value over the past 5 data points is less then 150 trigger

          Count is the combined total of the values for the past XYZ time period.

          It can take a little playing around with though, and if you haven't seen it there are pretty good definitions and examples in the docs.

          https://www.zabbix.com/documentation...gers/functions
          I think I may need to clarify, I also now understand count so thank you!

          What is the difference between MAX and MIN? I am having trouble understanding why the MAX.(300) OR MAX.(#5) fired on one event, where the MIN.(5m) fires on all values above the 150. My understanding was that min meant that only one value would cause it to fire within the 5 min time period and max, required all of them to meet. I know its wrong now, just looking for clarification for next time.

          Comment

          Working...