The following graphs illustrate the breakdown of a transaction to its layers, classes, and methods.
The following figure shows the top level Average Transaction Response Time graph. The graph displays several transactions: Birds, Bulldog, Checkout, Start, and so on.
In the following figure, the Start transaction has been broken down to its layers (DB, EJB, JNDI, and Web). In J2EE/.NET transactions, the Web layer is generally the largest.
In the following figure, the Web layer of the Start transaction has been broken down to its classes.
In the following figure, the weblogic.servlet.FileServlet component of the Web layer of the Start transaction has been broken down to its methods.
Note: Some JDBC methods can invoke SQLs which can be broken down further. In this case there is another level of breakdown, that is SQL Statements. For the methods that cannot be further broken down into SQL statements when reaching this level of breakdown, you see NoSql.
When a server request makes a remote method invocation, the J2EE & .NET Diagnostics graphs display certain measurements relating to the classes and methods involved in these requests. These measurements are displayed at a layer, class and method level. The VM making the call is referred to as the caller VM, and the VM that executes the remote call is the callee VM.
Descriptions of the measurements
Note: Since this data is measured on the caller virtual machine the exclusive latency will include all of the time required for making the remote method invocation such as network latency.