Integrating Triage Maps with Transaction Traces
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current diagnostic tools for computer systems lack the ability to effectively visualize flows through subsystems, making it difficult to diagnose problems in applications, especially when transactions fail, as they are too general or too specific, requiring users to switch between triage maps and transaction traces, which is cumbersome and requires extensive knowledge of software and infrastructure.
Innovation Solution
A method and system that visualizes flows through subsystems by displaying a triage map with nodes representing subsystems and arrows depicting dependency relationships, allowing users to overlay transaction traces on the map, providing detailed information and options to find transaction instances, and dynamically add instrumentation for deeper analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If diagnostic tools provide detailed transaction traces, then measurement precision is improved, but device complexity increases and ease of operation deteriorates
Solution Approach 1:
The diagnostic information is segmented into two distinct views: a high-level triage map showing subsystem relationships and a detailed transaction trace view showing individual component execution. Users can switch between these views or overlay them, allowing precise diagnostics through the detailed view while maintaining ease of operation through the high-level map.
Solution Approach 2:
The patent adds a spatial dimension to diagnostic visualization by displaying transaction traces overlaid on the triage map. This allows users to see both the high-level subsystem flow and detailed component traces simultaneously in different visual layers, resolving the contradiction between detail and simplicity.
2Measurement precision
If diagnostic tools switch between triage maps and transaction traces, then measurement precision is improved, but loss of time increases
Solution Approach 1:
The patent merges the triage map and transaction trace displays into a single integrated interface. The transaction trace can be overlaid on the triage map, allowing users to see both high-level subsystem relationships and detailed component execution without switching between separate tools or windows, thereby eliminating the time loss associated with switching.
3Measurement precision
If diagnostic tools require extensive software knowledge, then measurement precision is improved, but ease of operation deteriorates
Solution Approach 1:
The diagnostic interface is segmented into hierarchical levels: the triage map provides a simplified high-level view of subsystem relationships that requires minimal software knowledge, while the detailed transaction trace view provides in-depth component execution information for users with advanced knowledge. This segmentation allows users at different expertise levels to access appropriate diagnostic detail without being overwhelmed.
4Measurement precision
If diagnostic tools provide comprehensive transaction data, then measurement precision is improved, but device complexity increases
Solution Approach 1:
The interface is designed to be dynamic, allowing users to adjust the level of detail displayed. The transaction trace can be overlaid on the triage map at different levels of granularity, and users can selectively enable or disable specific trace components. This dynamic adjustability allows comprehensive transaction data to be presented without permanently increasing interface complexity, as users can simplify the view when full detail is not needed.
Data Source
Figure 1
Figure 2A~2C
Figure 3
AI summary
A method for diagnosing problems in a computer system by visualizing flows through subsystems of the computer system. Diagnostic tools include a user interface (122, 500, 520, 525, 530, 540, 550, 555, 556, 560, 570, 580, 590, 600, 610, 620, 630, 640, 650, 660, 670, 680) which includes a triage map (502) which graphically depicts subsystems, such as applications, through which a Business Transaction flows, and the calling relationship between the subsystems. The subsystems can be depicted by nodes (320, 321, 322, 324, 326, 328, 330, 336) which include alerts and performance information. The user can run a command to find transactions of a specific Business Transaction and/or front end subsystem which meet filter criterion such as response time and user identifier. Each captured transaction can be listed with information such as response time and reporting agent (108, 112, 116). Details of a particular transaction instance, such as its invoked components, can also be viewed in a transaction trace (401).