...
Alarm Correlation Rule Management
- Holmes provides basic rule management functionalities which allow users to design, create or modify rules via a rule designer.
Collect Alarms from Different Alarm Sources
- Holmes supports different kinds of alarm sources, including NFV, SDN and any other legacy systems (as long as the corresponding interfaces of the source system are exposed).
- Alarm Analysis
- Holmes can reduce alarms effectively by preventing duplicated alarms get into its downstream systems.Holmes can pick out the root cause from the ocean of alarms with the assistance of the topology information provided by other related systems.
- Persistence of the Results of Data Analyses
- All analytic results are written to DB for persistence.
- Holmes provides the functionality for users to view the statistical result of data analysis.
- Publish the Analytic Results to Subscribers
- Besides result persistence, Holmes publishes the analytic results to a specific topic. Any potential users can subscribe to the topic to get the results in real time.
Both Holmes and Policy adopt Drools as the rules engine. The main difference between these two projects is that Holmes is mainly aimed to accomplish correlation analysis of alarms while Policy is intended for policy-making. With the help of Holmes, a lot of alarms can be reduced so that downstream systems could focus on the innermost problem only.
For example, if there are 3 events A, B and C which could lead to a power down fault, and B and C are caused by A. Without Holmes, all of these 3 events will be sent to Policy and 3 corresponding action are triggered. After we add Holmes to the close loop controller and make it the upstream system of Policy, only A will be sent to Policy and thus only one action will be triggered, which makes the close loop control more precise and efficient.
Architecture Alignment:
...