842f9d6cea
- vitrage-graph will execute the drivers. - Simplify large data transfer from drivers to processor by obsoleting rpc. - Drivers don't need to create the complete list by taking advantage of python generators in order to conserve memory. - Lowering the total signiture of vitrage processes. - LockByDriver will enforce a driver does not run get_changes and get_all in parallel. Story: 2004384 Change-Id: Ie713456b2df96e24d0b15d2362a666162bfb4300
21 lines
957 B
ReStructuredText
21 lines
957 B
ReStructuredText
====================================
|
|
Root Cause Analysis service overview
|
|
====================================
|
|
|
|
Vitrage provides a root cause analysis service, which is used for analyzing the topology and alarms of the cloud, and providing insights about it.
|
|
|
|
The Root Cause Analysis service consists of the following components:
|
|
|
|
``vitrage-graph`` service
|
|
The main process. It includes the in-memory entity graph and the template evaluator.
|
|
Also responsible for retrieving data from the different datasources
|
|
``vitrage-notifier`` service
|
|
Used for notifying external systems about Vitrage alarms/state changes. It only calls Nova force-down API
|
|
and Simple Network Management Protocol (SNMP) in the Ocata release.
|
|
``vitrage-api`` service
|
|
The API layer for Vitrage.
|
|
``vitrage-ml`` service
|
|
Performs alarm analysis using Machine Learning methods.
|
|
``vitrage-persistor`` service
|
|
Used to persist the events coming from the datasources in a database.
|