Visualization of JVM and cross-JVM call stacks
First Claim
1. A computer-implemented method for visualizing flows through at least a first application, the method comprising:
- accessing a data store to access data regarding the first application, the data is obtained from an agent associated with the first application using instrumentation which is installed in the first application, the data represents multiple instances of the first application;
displaying a dependency graph on a user interface, the dependency graph graphically depicts;
(a) a first node which represents the multiple instances of the first application, (b) a second node which represents one subsystem on which the first application depends when a first preselected component of the first application is invoked, the first application is invoked in a first business transaction by virtue of the first preselected component being invoked, (c) at least one edge which represents a dependency of the first application on the one subsystem, (d) a node which represents another subsystem on which the first application depends when a second preselected component of the first application is invoked, the first application is invoked in a second business transaction by virtue of the second preselected component being invoked, and (e) another edge which represents a dependency of the first application on the another subsystem; and
responsive to a user selection of the first business transaction;
visually distinguishing the node which represents the one subsystem from the node which represents the another subsystem, and visually distinguishing the one edge from the another edge.
2 Assignments
0 Petitions
Accused Products
Abstract
A method for diagnosing problems in a computer system by visualizing flows through applications and other subsystems in a directed graph on a user interface. The user interface represents multiple instances of each application or other subsystem by a respective node, and edges indicate which nodes depend on one another. Aggregate metrics which are based on the multiple instances, and associated alerts, can be provided for the nodes and edges. An aging process can indicate which nodes have not been recently invoked. The user interface can also indicate which nodes and edges are associated with a given business transaction. In a summary view, a node hides the identity of invoked components such as servlets of the application, while in a detailed view these details are provided.
-
Citations
24 Claims
-
1. A computer-implemented method for visualizing flows through at least a first application, the method comprising:
-
accessing a data store to access data regarding the first application, the data is obtained from an agent associated with the first application using instrumentation which is installed in the first application, the data represents multiple instances of the first application; displaying a dependency graph on a user interface, the dependency graph graphically depicts;
(a) a first node which represents the multiple instances of the first application, (b) a second node which represents one subsystem on which the first application depends when a first preselected component of the first application is invoked, the first application is invoked in a first business transaction by virtue of the first preselected component being invoked, (c) at least one edge which represents a dependency of the first application on the one subsystem, (d) a node which represents another subsystem on which the first application depends when a second preselected component of the first application is invoked, the first application is invoked in a second business transaction by virtue of the second preselected component being invoked, and (e) another edge which represents a dependency of the first application on the another subsystem; andresponsive to a user selection of the first business transaction;
visually distinguishing the node which represents the one subsystem from the node which represents the another subsystem, and visually distinguishing the one edge from the another edge. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16)
-
-
17. At least one tangible, non-transitory, processor-readable storage device having processor-readable software embodied thereon for programming at least one processor to perform a method for visualizing flows through respective applications, the method performed comprises:
-
accessing a data store to access data which is obtained from respective agents associated with the respective applications, the respective agents provide the data using instrumentation which is installed in the respective applications, the data represents multiple instances of each of the respective applications; displaying a dependency graph on a user interface, the dependency graph graphically depicts;
(a) a first node which represents multiple instances of one application of the respective applications, (b) a second node which represents multiple instances of another application of the respective applications, and (c) at least one edge which represents a dependency of the one application on the another application, the one application depends on the another application when a first preselected component of the one application is invoked, the one application is invoked in a first business transaction by virtue of the first preselected component being invoked, and the one application depends on the another application when a second preselected component of the one application is invoked, the one application is invoked in a second business transaction by virtue of the second preselected component being invoked; andresponsive to a user selection of the first business transaction;
setting an alert icon for the first node based on aggregated metrics across the multiple instances of the one application which were invoked in connection with the first business transaction but not in connection with the second business transaction. - View Dependent Claims (18, 19, 20)
-
-
21. A computer-implemented method for visualizing flows through at least a first application, comprising the computer-implemented steps of:
-
accessing a data store to access data regarding the first application, the data is obtained from an agent associated with the first application using instrumentation which is installed in the first application, the data represents multiple instances of the first application; displaying a dependency graph on a user interface, the dependency graph graphically depicts;
(a) a first identifier which represents a first business transaction in which the first application is invoked, (b) a node which represents the multiple instances of the first application, (c) a node which represents one subsystem on which the first application depends, in connection with the first business transaction, (d) one edge which represents a dependency of the first application on the one subsystem in connection with the first business transaction, (e) a second identifier which represents a second business transaction in which the first application is invoked, (f) a node which represents another subsystem on which the first application depends, in connection with the second business transaction, and (g) another edge which represents a dependency of the first application on the another subsystem in connection with the second business transaction; andresponsive to a user selection of the first identifier which represents the first business transaction, visually distinguishing the node which represents the one subsystem over the node which represents the another subsystem, and the one edge over the another edge. - View Dependent Claims (22, 23, 24)
-
Specification