THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Design tables: metricSchemaDef, metricGroupDef, policyDef
- Storm topology: one spout + N correlation bolts
- Spout
- reference KafkaSpout, but may need some fundamental changes if we want support multiple topic
- maintain a route table which maps metricGroup to correlation bolt ID. This table should be identical across all spout instances
- read metricGroupDef and metricSchemaDef in background and spawn new thread to read new metric
- Correlation bolt
- read policyDef
Engineering Design
Gliffy Diagram | ||||
---|---|---|---|---|
|
Implementations:
- Example code is under https://github.com/yonzhang/incubator-eagle/tree/hackillinois
- eagle-examples/eagle-correlation-engine topology example to wrap multiple KafkaSpout into one spout
- eagle-examples/eagle-correlation-service service example to provide API to read/write metadata, for example metric, metric group etc.