Alert with multiple conditions does not honor metric collection interval

Solution Unverified - Updated -

Issue

  • An alert that should be fired when ALL conditions are fulfilled may be triggered although it's conditions are not fulfilled at the same time;
  • We defined an alert that should be fired when ALL conditions are fulfilled where conditions are:
    • Metric Value Threshold [Inflight Exchanges > 0.0]
    • Metric Value Threshold [Exchanges Completed per Minute = 0.0]
  • Sometimes we get false alarms where condition1 and condition2 timestamps seem to differ more then 20 minutes (metric collection interval is 20 minutes for both measurements) - sometimes it's been more then few hours difference;
  • We got the following alert:
Subject: [ALERT] priority of [Medium] for alert [Alert - Camel Route Stalled] on resource [file-to-jms-route Route]

The resource file-to-jms-route Route has generated the following alert:

------------------------------------------

Resource Name    : file-to-jms-route Route
Alert Name       : Alert - Camel Route Stalled
Alert Severity   : Medium
Alert Date/Time  : Mon May 25 15:25:43 BST 2015
Conditions: 
  - Condition 1: Inflight Exchanges > 0.0
  - Date/Time: 2015/05/25 15:25:28 BST
  - Details: 1.0

  - Condition 2: Exchanges Completed per Minute = 0.0
  - Date/Time: 2015/05/25 14:27:55 BST
  - Details: 0.0


------------------------------------------

Resource Ancestry:

stever.fab.redhat.com [Platforms, Linux]
  JBoss Fuse{/home/ingo/jboss-fuse-6.1.0.redhat-379} JBoss Fuse [root] [JBossFuse, JBoss Fuse Container]
    org.jboss.quickstarts.fuse.jms jms-example-context Camel Context 2.12.0.redhat-610379 [Camel, Camel Context]
        file-to-jms-route Route [Camel, Camel Route]

although "Exchange Completed per Minute" was not 0.0 at the time when "Inflight Exchanges" was > 0.0.

Environment

  • Red Hat JBoss Operations Network (JON) 3.3
  • Red Hat JBoss Fuse 6
  • Created and configured an alert on Camel Route resource; This alert should be triggered when ALL conditions are fulfilled and conditions are:
    • Inflight Exchanges > 0.0
    • Exchanges Completed per Minute = 0.0
  • Collection period for metrics Inflight Exchanges, Exchanges Completed per Minute and Exchanges Completed set to 20 minutes;

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.