{TRIGGER.VALUE} macro incorrectly allowed in aggregate functions in trigger/recovery expressions

XMLWordPrintable

    • S24-W24/25
    • 1

      Hello Team,

      In trigger configuration form the trigger expression as well as recovery expression fields accept {TRIGGER.VALUE} macro as item filter/key within aggregate functions syntax. Please see example below:

      max({TRIGGER.VALUE},15m)=1
      

      {TRIGGER.VALUE} represents current trigger state as numeric value, so there is nothing to be aggregated. This may cause triggers to incorrectly fire an alert or not being resolved at all.

            Assignee:
            Arkadiusz Zyla (Inactive)
            Reporter:
            Arkadiusz Zyla (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: