Craig Bryant 63290a82ab JIRA JAH-10 On start-up threshold engine should wait for metrics for all periods prior to transitioning to an alarmed state ... Change so that all view slots must have metrics before the SubAlarm transitions to ALARM. Also, change it so SubAlarmStats doesn't transition it to UNDETERMINED on startup until there have been emptyWindowObservationThreshold calls to evaluate(). Previously it only required one for new sub alarms and sub alarms on restart. Want the ThresholdEngine to have same behavior on restart as it would when the Threshold Engine has been running for a long time.		2014-04-28 16:38:35 -06:00
..
domain	JIRA JAH-10 On start-up threshold engine should wait for metrics for all periods prior to transitioning to an alarmed state	2014-04-28 16:38:35 -06:00
infrastructure	JIRA JAH-10 On start-up threshold engine should wait for metrics for all periods prior to transitioning to an alarmed state	2014-04-28 16:38:35 -06:00
EventSpoutConfig.java	Mark more config classes Serializable so they can be used in Storm	2014-03-12 15:43:25 -06:00
MetricSpoutConfig.java	Mark more config classes Serializable so they can be used in Storm	2014-03-12 15:43:25 -06:00
ThresholdingConfiguration.java	Implemented KafkaAlarmEventForwarder to actually use Kafka. Has not been tested, yet, but pretty simple implementation.	2014-03-14 15:39:04 -06:00
ThresholdingEngine.java	Added logging.	2014-03-20 07:42:05 -06:00
TopologyModule.java	JIRA JAH-11 Keep Alarms from switching to UNDETERMINED if the Threshold Engine has been down for long enough that Kafka has buffered enough Metrics that it takes the Threshold Engine minutes to catch up.	2014-04-23 17:12:50 -06:00