Root Cause & Impact Analysis
Too much time searching for the root cause the incident and its business impact
Without understanding what each incident affects it’s impossible to make a clear incident prioritization. To speed up incident investigation time you need to understand the root cause of the problem it can be difficult to determine due to the high complexity and volume of the infrastructure.
Root Сause and Impact Analysis as a solution
Impact analysis is needed to understand how much the problem affects the business and which problem takes priority.
Root cause analysis helps recognize what you should do first to solve the incident.
How does it work?
1. First, configure Data Streams. Utilize the connector for existing systems or create the custom connectors for the systems that don’t already exist in Acure. Process the tasks for integration and start the collection of data.
2. After collecting the data and correlation setup, you can see the status of the entire IT infrastructure on a single screen. It is visible on the maps, plus you can program it via scripts.
There are three types of root cause analysis in Acure:
Root cause by topology
Topology shows the whole IT infrastructure like a tree with the relationships between configuration items. You can see the health of root CI and easily identify the problem item using the connections elements on the graph.
Root cause by time
Using Acure, you can easily visualize all events by filtering the necessary timeline, recognizing why some elements didn’t work in the specific timeframe.
Root cause by context
Find the root problem by analyzing events and logs. Use the Logs and Events screen to view raw data, logs, and messages coming into Acure from various data streams.