Root Cause Analysis
Why Root Cause Analysis Is Difficult
As the topology of distributed, interconnected applications becomes more complex, the challenge of fast, easy root cause analysis of any underlying IT infrastructure processing problems increases. Performance and availability issues often appear in systems that may be upstream from the root cause. Full diagnostics require a roadmap of the problematic transaction to address the issue and expedite problem resolution.
But in environments employing distributed, interconnected applications root cause analysis is difficult. These applications often execute on heterogeneous systems that reside in different locations and are owned by different groups.
As a result, diagnostics often take a lot of time—generating IT costs. In addition, until the problem is resolved, the affected processes may slow down, display incorrect data, or even shut down completely—in each case adversely effecting end users.
Progress Actional Enterprise: Making Root Cause Analysis Faster and Easier
Progress® Actional® Enterprise makes finding the root cause of exceptions and violations of business policies such as service-level agreements (SLAs) easy. When violations occur, along with sending an alert, Actional's Flow Mapping™ technology creates a flow map of the end-to-end problematic transaction.
Figure: Flow maps show all service dependencies and highlights the violating paths.
The flow map above shows all service dependencies and highlights the violating paths or links. IT administrators can drill down and see processing statistics for each service—to quickly and easily trace the issue back to its source and speed problem resolution. As a result, transactions are more reliable, reducing management costs and maintaining the pace of business and customer service.
You may also be interested in...
Related Topics
- Service-level Management
- Transaction Monitoring and Alerting
- Exception Management
- Multi-site Integration
