Reviewing the trace list for a selected transaction

A trace is the entire path of a request, from the client system to the server system. For example, in a web application, a trace describes the path of a user request made through a web browser, to each of the back-end servers, including web presentation servers, business servers, and databases.

A trace is recorded if it is considered relevant according to the App Visibility configuration and thresholds. For details about modifying threshold settings, see Configuring event thresholds (SLAs) for automatically discovered applications.

The traces of a selected business transaction or request are displayed, filtered by the selected time range. If the application server filter is used (which is the default) on the Business Transactions page, then the traces are also filtered by the server.

By default, traces are displayed in descending order, according to the latency value.

Diagnostics data of traces

The following table describes the diagnostics data in the Traces page.



Action menuSelect Show Trace Details to examine the details of a specific trace


Classification of the transaction, either as a full business transaction or as single request within the transaction


IP address or name of the application server on which the trace occurred


Date and time the trace began on the application server


Error captured during the trace, indicates that the trace ended in an error, or that an internal error (exception) occurred


Duration (0m 0s 000ms) of the trace

Filtering the time range of the trace list

When you drill down from the business transactions, traces are automatically filtered by the same time range.

You can adjust the time filter to examine traces over time.

To change the time range

  1. Click the action menu next to the currently selected time range.
  2. Select a predefined time range from the menu, or select Customize to enter a different time range.
  3. If you select Customize, select a Start time and an End time, and click Done.
    Ensure that the start time is earlier than the end time.

The time range is modified, and the displayed data reflects the change in the time range.

The collected data and metrics are recalculated and updated every five minutes.

Navigating the interface

Move between pages of the Application Monitoring and Application View interface.

  • To return to the Application page, click the arrow next to the page Application Monitoring title.
  • To move up from the drill-down pages of the Application View, click a breadcrumb titles. For example, to move from the Business Transactions page to the Application View page, click the title. Likewise, after you drill-down to Traces and Trace Details, you can easily move back using the breadcrumb titles.

Navigation elements in the Application Monitoring page

Where to go from here

After pinpointing a trace that you want to analyze, click the name to view diagnostics data for that specific instance. Diagnostics data includes server information and statistics, technology tier data, the application flow of the transaction, and the code segment for that transaction.

Related topics

Analyzing business transactions

Analyzing user transaction details

Investigating severity and impact of application issues

Was this page helpful? Yes No Submitting... Thank you