Uploaded image for project: 'Hawkular Metrics'
  1. Hawkular Metrics
  2. HWKMETRICS-630

Metrics Alerters could use a native way of preventing alert repetition

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 0.26.0
    • Component/s: Alerting
    • Labels:
      None

      Description

      The Metrics Alerter condition expression offers the ALL and EACH EvalTypes. The EACH eval type means the expression is evaluated for each metric targeted by the query. This is good because one trigger definition can apply to many different metrics. But the downside is that using autoDisable or AutoResolve options on the trigger becomes difficult. If the trigger fires because of one metric, and then disables, it may miss issues for other metrics in the target set. Autoresolve has the same issue whil also being hard to apply due to the varying variety of metrics than may have fired the trigger.

      Although not a replacement for the trigger-level options, it could be useful to have an option on the ConditionExpression that would suppress redundant firing for the same metric until that metric has returned to a steady state.

      The proposal is to add the 'quietCount' option to the ConditionExpression. If set it would mean: after a send, stay quiet (no resend) until after we see N false evaluations. It would apply to each metric individually.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jayshaughnessy Jay Shaughnessy
                  Reporter:
                  jayshaughnessy Jay Shaughnessy
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: