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.
Column | Description |
|---|---|
| Action menu | Select Show Trace Details to examine the details of a specific trace |
Type | Classification of the transaction, either as a full business transaction or as single request within the transaction |
Server | IP address or name of the application server on which the trace occurred |
Start | Date and time the trace began on the application server |
Error | Error captured during the trace, indicates that the trace ended in an error, or that an internal error (exception) occurred |
Latency | 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.
If you select Customize, select a Start time and an End time, and click Done. The time range is modified, and the displayed data reflects the change in the time range.To change the time range
Ensure that the start time is earlier than the end time.
The collected data and metrics are recalculated and updated every five minutes.
Move between pages of the Application Monitoring and Application View interface. Navigation elements in the Application Monitoring pageNavigating the interface
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
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks