Analyzing web page problems with the User tier

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.

No data in the User Tier?

One or both of the following conditions can cause the User tier to be blue and have a status of No Data:

The application is not associated with an Agent.
Thresholds are not set for the application.

To analyze web page problems with the User tier

Click the User Tier box to display the application pages in the Pages section.
Scroll through the Pages viewor sort columns to review the severity of page problems.
View the traces associated with the business transaction for a selected page.
Using the check boxes, select pages to display in the Problems view.

User tier status

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	Blue (No Data). No data was collected, usually because integration with BMC Application Diagnostics is not implemented or configured, or the application was not associated to an Agent or configured. Green (No Problems). Percentage of slow pages did not exceed the application thresholds Orange (Warning). Percentage of pages exceeded the Warning threshold Red (Critical). Percentage of pages exceeded the Critical threshold
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.

Pages view

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:

Check box that you can use to select one or more pages to view in the Analysis view.
Short-cut menu that enables you to view the traces for the business transactions of the page

When you select View Traces from the shortcut menu, the transactions for the selected page and time period appear in the Query Details on the Traces page.
Severity of the page

A page with No Problems can still have performance problems, but fewer than the percentage required to exceed the Warning or Critical threshold.

Page name
Average end-to-end time observed for that page across all users of the application
Percentage of pages whose end-to-end times exceeded the E2E threshold time for the application.

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

Problems view

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:

Severity of the threshold violation, which is indicated by color and the severity label
Name of the page and problem detected on the page that caused the poor performance
Percentage of pages that exceeded the E2E threshold and the threshold value that was exceeded
Time in which the problem occurred
Open or Closed, which represents the current status of the problem, and time in which the problem was resolved, if applicable

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.

Seeing different values in the two reports?

The value for latency violations in the Pages report is updated every five minutes, and the similar value in the Problems report is updated when the status of the problem changes. Because the update intervals of these two sections differ, the values in the two reports might not always match.

Example Problems view