Ad Widget

Collapse

trigger fires on the "wrong" value

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • sitnikov
    Junior Member
    • Jan 2010
    • 15

    #1

    trigger fires on the "wrong" value

    Trigger event

    Click image for larger version

Name:	Screenshot 2021-05-11 at 15.46.06.png
Views:	145
Size:	21.5 KB
ID:	424429

    Trigger config

    Click image for larger version

Name:	Screenshot 2021-05-11 at 15.49.09.png
Views:	152
Size:	151.5 KB
ID:	424430


    {$SUPPLY_WATTER_HIGH_LIMIT} == 18

    I don't understand why the trigger was fired.


    Zabbix 5.2.6
  • luisamaral
    Junior Member
    • Aug 2018
    • 15

    #2
    Can you post a graphic of this item?

    Sometimes the average value is above the limit, but the last value is less than the limit

    To solve this problem, change the average function to minimum. Thus, the lowest value collected will be analyzed and not their average.

    If in the last 5 minutes the lowest value is 18, probably this metric has already crossed the limit

    Comment

    • sitnikov
      Junior Member
      • Jan 2010
      • 15

      #3
      Graph attached
      Attached Files

      Comment

      • luisamaral
        Junior Member
        • Aug 2018
        • 15

        #4
        Originally posted by sitnikov
        Graph attached
        Try make the changes I said and tell me the result

        Comment

        • sitnikov
          Junior Member
          • Jan 2010
          • 15

          #5
          I understand this workaround. I'm more interested in why is {ITEM.VALUE1} below 18 (as we can see in description) and trigger fired

          Comment

          • luisamaral
            Junior Member
            • Aug 2018
            • 15

            #6
            Originally posted by sitnikov
            I understand this workaround. I'm more interested in why is {ITEM.VALUE1} below 18 (as we can see in description) and trigger fired
            Because the macro will show the item's value at the moment the trigger is fired.

            And the most recent value is not necessarily higher than the configured limit value.

            Comment

            Working...