Tomasz Trębski 080b11dc54 (Non)deterministic alarm processing ... 'deterministic' being part of alarm expressions allows monasca-thresh to determine if given alarms can go back to UNDETERMINED state or not. 'deterministic' means that alarm won't ever transititon to UNDETERMINED state, even if there are no measurements received for long enough. By default, all alarms are assumed to be 'non-deterministic' which means that they can transition to 'UNDETERMINED' state Implements: blueprint alarmonlogs Depends-On: Ia42f9a1be37c31416bdac341b092fe527f860c16 Change-Id: Ibe0839123a15494ad45b809e68600c0acef3d330		2016-06-07 12:00:58 +02:00
..
domain/model	(Non)deterministic alarm processing	2016-06-07 12:00:58 +02:00
infrastructure	(Non)deterministic alarm processing	2016-06-07 12:00:58 +02:00
Assert.java	Change packages to monasca.thresh	2014-08-05 22:03:47 -06:00
ThresholdingEngineAlarmTest.java	Clean up orphaned alarms on alarm definition delete	2015-05-08 12:31:22 -06:00
ThresholdingEngineTest.java	(Non)deterministic alarm processing	2016-06-07 12:00:58 +02:00