[Hawkular-commits] [hawkular/hawkular-alerts] 89c0af: An attempt at Strict_Timeout dampening, the abilit...

[Jay Shaughnessy]

  Branch: refs/heads/winter/stricttimeout
  Home:   https://github.com/hawkular/hawkular-alerts
  Commit: 89c0afd1dcb470b143d1777aa3c1fcf23d5d6b02
      https://github.com/hawkular/hawkular-alerts/commit/89c0afd1dcb470b143d1777aa3c1fcf23d5d6b02
  Author: Jay Shaughnessy <jshaughn at redhat.com>
  Date:   2015-03-19 (Thu, 19 Mar 2015)

  Changed paths:
    M hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/dampening/Dampening.java
    M hawkular-alerts-engine/src/main/java/org/hawkular/alerts/engine/impl/BasicAlertsServiceImpl.java
    M hawkular-alerts-engine/src/main/java/org/hawkular/alerts/engine/impl/DroolsRulesEngineImpl.java
    M hawkular-alerts-engine/src/main/java/org/hawkular/alerts/engine/rules/RulesEngine.java
    M hawkular-alerts-engine/src/main/resources/org/hawkular/alerts/engine/rules/ConditionMatch.drl
    M hawkular-alerts-engine/src/test/java/org/hawkular/alerts/engine/RulesEngineTest.java

  Log Message:
  -----------
  An attempt at Strict_Timeout dampening, the ability to fire a trigger
N ms after a condition set becomes true, if that condition set does not
eval to false before the timer is up.

This approach does not rely on drools stream mode/cep, but rather
defers the timer handling externally, thus maintaining discrete rule engine
executions.