Analyzing user transaction details

Analyze user transactions to locate transaction entry points or requests that are slow or have errors that could be impacting your users. User transactions refer to performance and availability data collected from end-user browsers.

The user transactions table displays statistics for the selected five-minute period. By default, the user transactions are sorted in descending order by number of users, so that you can quickly see the issues that impact the largest number of users.

User transaction statistics include the following kinds of requests:

Page: Web requests (such as .../login.jsp or .../strutsServlet?action=logout)
AJAX: Asynchronous JavaScript and XML (AJAX) exchanges with a server that is monitored by an App Visibility agent
External Service: AJAX requests to a server that does not have an App Visibility agent. The external service requests can display end-to-end time, but not server and network duration.
Transaction: Requests without end-user monitoring through the App Visibility proxy. These requests, such as requests from native mobile applications, cannot display end-to-end time or other time details..

This topic describes the contents of the user transactions table, which you can see after drilling down from the User tier. Data is displayed in the user transactions table according to the selected filters.

User transactions table

The user transactions table displays data for the selected five-minute period.

The following table describes the contents of each column in the table.

Contents of the user transaction table

Column	Description
Name	Name of the request
Type	Type of request: Page, AJAX, Transaction, or External Service
Total	Number of users that invoked the request
With Errors	Percentage and number (in parentheses) of users that experienced availability issues
With Latency Violation	Percentage and number (in parentheses) of users that experienced performance issues, exceeding the E2E time threshold for the application
Avg E2E Latency	Average end-to-end time (0m 0s 000ms) of the web page transactions
Hit Count	Number of requests

Note

App Visibility Manager adds the BMCTSEUM cookie to the browsers of end users and reads the cookies to monitor user experience. If the cookie is removed or disabled, you can see partial data from end users: the average end-to-end time and the hit count.

Examining latency breakdown

Examine the latency breakdown of a user transaction to help locate the source of latency and understand where to investigate. The latency breakdown shows server, network, and browser times.

Select a request in the table to show the Average Latency Breakdown chart for the request.
- The chart displays the server, network, and browser times, which are stacked to show the total latency.
- A pointer shows the end of the selected five-minute period.
Hover over an area of the chart to see the breakdown of the components impacting the transaction latency.

Average latency breakdown chart

Filtering user transactions

When you drill down to user transactions from User tier, the transactions are automatically filtered by the selected five-minute period. You can use the following filters to help locate the transactions that you want to evaluate:

To change the time range
To filter by transaction summaries

To change the time range

You can change the selected five-minute period to see how your users are impacted.

Examine previous or next five-minute period. Click the left and right arrows of the five-minute time picker to change the selection by five minutes.
Select a specific five-minute period.

1. Click the Date action menu.
2. Select a date and time.
  The time represents the end of the five-minute period.
3. Click Done.

To filter by transaction summaries

The summary filter enables you to quickly see the problematic transactions in the selected five-minute period.

Click the relevant summary box to display all transactions, or to display only the transactions that have latency violations or errors.

Example

Summary filter example

You can filter transactions in the following ways:

Click Latency Violations to display the transactions that exceeded the defined performance thresholds.
Click Errors to display the transactions with errors that exceeded the defined availability thresholds.
Click both summary filters to display all transactions that have latency violations, errors, or both.
Click All Transactions to display all transactions, including transactions without issues.

Where to go from here

Analyzing diagnostics data for a trace

Page tree