The Browse Resources screen shows information for all types of applications, but it is especially effective (and shows the most detail) for Spring, Grails, and Roo applications.
From the main Spring Insight dashboard, click the Browse Resources link:
On the left, the root tree node, All Applications, is selected in the APPLICATIONS panel and All Servers is selected in the SERVERS panel. The APPLICATIONS HEALTH TREND panel displays a graph of the recent health of all applications on all servers. The APPLICATIONS panel on the right, beneath the graph, displays a list of the applications with some statistics for the application for the time period displayed by the graph:
The Health Trend column shows a simple sparkline that graphically describes the recent health of the application.
The Throughput column shows how many Traces per Minute (tpm) were executed over the current time window.
The Errors column shows what percentage of Traces resulted in an Error (HTTP status 500 to 600).
The graphical or tabular view of all applications is useful to see which applications have been busiest and to compare their relative health. Click in the graphs to see the application-specific information. Click the column headers in the table to sort the information based on the values in the column.
The SERVERS panel at the bottom of the right column displays the same statistics for each server in the cluster. From this list, you can easily identify underperforming or failing servers.
With All Applications selected in the left APPLICATIONS panel, click on an individual server in the left SERVERS panel. This view displays a Health Trend graph for all applications running on the selected server and detailed information for the server.
The heading of the graph panel changes to identify the server you selected. The Vitals section of the graph panel displays performance statistics for the server for the time period depicted on the graph:
Throughput: how many Traces per Minute (tpm) were executed during the current time window.
Invocations: the total number of requests made during the current time window.
Error rate: the percentage of invocations that resulted in an HTTP error status.
The Properties section of the graph panel lists system property settings for the server:
catalina.base: the home directory for the tc Runtime instance.
date.creation: the date the tc Runtime instance was created.
java.pid: the process ID of the Java VM.
system.net.connecting.ip: needs description
system.net.default.route.ip: needs description
system.net.ip: needs description
system.net.name: The network name of the host computer.
Expand the All Properties list at the bottom to see a complete list of tc Server and Java system properties.
Click on an application in the left APPLICATIONS panel and All Servers in the left SERVERS panel. The right panel displays information about the selected application and its End Points across all servers in the cluster. The END POINTS panel displays the End Points associated with the application; the same list appears below the name of the application in the left APPLICATIONS panel.
The Vitals section in the graph shows a summary of the health of the application.
Each row in the End Points table represents an End Point, which is a receptor for requests. The universe of all possible HTTP URLs is unlimited. However, Spring Insight can group requests together based on the controller with which the requests are associated. For each End Point, Spring Insight displays the following information:
Health: Shows how well the response time metric is kept within a tolerable threshold, where red is less healthy and green is more healthy. See Customizing End Point Thresholds for setting the tolerable threshold.
End Point: Displays the name of the End Point.
Throughput Trend: Displays a simple sparkline that shows the recent mean throughput time of the End Point.
Throughput: Shows how many Traces per Minute (tpm) were executed over the current time window.
Errors: Shows what percentage of Traces resulted in an Error (HTTP status 500 to 600).
Response Time : Displays the 99% response time over the given time range. This value is most useful to determine the worst-case request. A value of 115 ms indicates that 99% of the requests completed within 115 milliseconds. The response time of an HTTP request is determined by the full time it takes the container to ship the response to the client, and not just the time spent in a controller.
Click on any individual server in the left SERVERS panel to see the same information described in the previous step for just the selected server.
Click on a particular End Point, either in the left APPLICATIONS panel or in the right END POINTS table for a particular application:
Spring Insight displays the following detailed information about the End Point:
The chart shows the throughput, response time, and error rate trends on the same graph. Response time trend refers to the mean response time of the End Point over the time range. Throughput trend refers to the recent mean throughput time of the End Point. Error rate is the percentage of traces resulting in an HTTP error. Click on markers (points) in the chart to view Trace data that occurred during that time range.
The RESPONSE TIME HISTOGRAM is an interactive graph that shows how many invocations occurred within a given time period. The Y-axis represents the response time of an invocation. The X-axis represents the number of invocations. Using the histogram is an easy way to identify outliers in your data. The longest-running invocations are always at the top of the histogram. If extreme outliers exist, they are indicated by red bars.
The Health of the End Point is determined by the Response Time for requests made over the given time interval. The response times are broken down into various Health Zones (such as frustrated , tolerated or satisfied . Click on a particular Health Zone to see representative Traces within that zone.
Click a bar in the histogram or on one of the markers in the Throughput or Response Time Trend graphs. A REPRESENTATIVE TRACES panel shows representative traces for some invocations that occurred during the selected duration.
The REPRESENTATIVE TRACES panel includes similar data as that of the Recent Activity screen. From here it is easy to drill into the shortest or fastest running traces to see what made them different. See Viewing Recent Activity of Your Application for detailed information about traces and trace details.