[Hawkular-commits] [hawkular/hawkular-alerts] f27eb0: An attempt at Strict_Timeout dampening, the abilit...
Branch: refs/heads/wintermute
Home: https://github.com/hawkular/hawkular-alerts
Commit: f27eb029d229d17a55fd5938b1e2e6f6b62413af
https://github.com/hawkular/hawkular-alerts/commit/f27eb029d229d17a55fd59...
Author: Jay Shaughnessy <jshaughn(a)redhat.com>
Date: 2015-03-26 (Thu, 26 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.