The following procedure describes how to browse through all the applications deployed to the tc Runtime instance, as well as their associated End Points, and view their health, throughput trends, response time trends, and response time histograms.
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:
The Applications panel on the left displays a resource tree of all applications that have reported Traces; you can expand each application to see its list of End Points. The health of the application is displayed next to its name and represents the worst-performing End Point within the Application. Each End Point also displays its health, which is described later on in this procedure.
Spring Insight loads the resource tree when it initially loads the page. If you subsequently deploy a new application or Spring Insight detects new End Points, it automatically adds these resources into the resource tree.
The Applications Health Trend panel on the right shows a graph of the recent health of all applications. Each application has its own color so you can differentiate them. The lower panel lists the same applications in tabular form, along with the following information about each application:
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 column.
Click on an application in the left Applications panel. The right panel displays similar information about the application as in the previous table, but this time the graph contains information only about the specific application and its End Points. 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 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 controllers 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 help setting the tolerable threshold.
End Point: Displays the name of the End Point.
Health Trend: Displays a simple sparkline that shows the recent health 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 95% response time over the given time range. This value is useful to determine the worst-case request. A value of 115ms indicates that 95% of the requests completed within 115 milliseconds. The response time of an HTTP request is the full time the container takes to send the response to the client, not just the time spent in a controller.
Click on a particular End Point, either in the left Applications panel or in the right End Points table:
Spring Insight displays the following detailed information about the End Point:
The End Point chart shows the throughput trend, response time trend, and error rate. 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. The error rate shows the percentage of traces that resulted in an error. Hover over any spot in the chart to view details for the time slice represented by that section of the chart. Click on a data point to see trace data that occurred during that time range.
The Vitals section displays the mean throughput, total number of Invocations, and errors for all of the traces in the time range represented on the current chart.
The Response Time section displays statistics about the response times for all of the traces represented on the current chart. The 95th Percentile statistic indicates that 95 percent of requests completed within the indicated time period. The Mean is the average response time. The Standard Deviation is a measure of the variability of response times. A larger standard deviation indicates a greater variability in response times.
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.