...
Scope:
Alarm Correlation Rule Design & Creation
Input original alarms from alarm source
- Output analysis results to subscriber
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.
- Basic Analysis
- Root Cause Analysis
- Service Impact Analysis
Architecture Alignment:
Holmes is a an application that processes events published by managed resources or other applications that detect specific conditions. Based on defined root cause analysis rules about the network, an application of this kind would determine root cause for various conditions and notify other interested applications.
Holmes consists of a rule designer and a correlation engine.
Real-time Analytic application get the analysis result, which is the root cause can be used to drive the policy runtime for automation operation.
Correlation Engine receives original alarms from monitor and output the result back to monitor after analysis based on rules and the resources relationships from AAI.
Rule Designer provides a user-friendly GUI to design the Correlation rules.
Resources:
Role |
---|
...
Name | Gerrit ID | Company | Email | TimeZone | |
---|---|---|---|---|---|
Primary Contact | Guangrong Fu | ZTE | Beijing, China. UTC +8 | ||
Commiters | Guangrong Fu | ||||
Peng Tang | ZTE | tang.peng45@zte.com.cn | Beijing, China. UTC +8 | ||
Contributors | Jiaqiang Du | ZTE | du.jiaqiang@zte.com.cn | Beijing, China. UTC +8 | |
Yi Li | ZTE | li.yi101@zte.com.cn | Beijing, China. UTC +8 | ||
Youbo Wu | ZTE | Beijing, China. UTC +8 | |||
Liang Feng | ZTE | feng.liang1@zte.com.cn | Beijing, China. UTC +8 |
...
Other Information:
- link to seed code (if applicable)
git clone https://gerrit.open-o.org/r/holmes-actions
git clone https://gerrit.open-o.org/r/holmes-engine-management
git clone https://gerrit.open-o.org/r/holmes-gui
git clone https://gerrit.open-o.org/r/holmes-rule-management - Vendor Neutral
- if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
- Meets Board policy (including IPR)
...
Repo name:holmes
Lifecycle State:
Primary Contact: Guangrong Fu (fu.guangrong@zte.com.cn)
Project Lead: Guangrong Fu (fu.guangrong@zteguangrong@zte.com.cn)
mailing list tag [Should match Jira Project Prefix]
Committers:
fu.guangrong@zte.com.cntang.peng@zte.com.cnPlease refer to the table above.
*Link to TSC approval:
Link to approval of additional submitters: