If you set Warning and Critical thresholds for the application, the User tier provides a visual indication about the page performance compared to the thresholds. This topic describe how to use the User tier to identify performance and availability problems in your application.
When the selected time period on the Application View page displays the User tier with the Critical (red) or Warning (orange) severity, application web pages have exceeded the Warning or Critical thresholds established for your application. By clicking the User tier, you can begin inspecting all pages, or filter the list to pages that contained problems.
The following table describes the meaning of the values and colors for the selected time segment of the User tier:
User tier description
Attribute | Description |
---|---|
Color and status |
|
Latency Violations | Percentage of pages where the end-to-end page times exceeded the E2E threshold for the application |
Avg Latency | Average end-to-end time of all pages in the application, in milliseconds |
Example User tier
In this example, the User tier shows that 60% of the pages in the application exceeded the E2E threshold and that the average latency across pages in the application was 936 milliseconds.
Clicking the User Tier box populates the Page severity with page severity information.
The Pages view lists the pages in the application in decreasing order by page end-to-end time. By default, this view shows only pages that contained errors, but you can modify the view content by adjusting the Pages filter to show all pages. You can also change the order of pages in the view by clicking any of the column headings. The Pages view provides the following information for each page:
In the following example, two of the pages had end-to-end times that exceeded the Critical threshold for the application and one page exceeded the Warning threshold. The page with the slowest time is listed first, and is selected. Additional details about the selected page appears in the Analysis view.
The View Traces menu option appears when you hover over the corresponding action menu for a page.
Example Pages report
When you select one or more rows in the Pages view, details about the page problems appear in the Analysis section in the Problems view, as shown in the following example. Each problem appears in a separate row. Because a page can have more than one problem, the Problems view can contain two rows for a page. For each problem detected on the page, the view provides the following information:
In the following example, one error contributed to the current severity of the selected page by exceeding the Critical E2E threshold for the application, which is 80%. The Analysis view also shows the time at which the problem was closed. At the time in which this report was viewed, the pages did not have problems, which is indicated by the green text of the current status.
Example Problems view
Monitoring application health and performance
Analyzing application server problems with the Web, App, and Business tiers
Analyzing database problems with the Database tier
Reviewing the trace list for a selection