Reviewing the trace list for a selection

A trace is a single interactions between the client system and the server system. In a web application, the interaction is between the browser and the server.

A trace is recorded if it is considered relevant according to the configuration thresholds of the BMC Application Diagnostics Agents. For details about modifying threshold settings, see Modifying-an-agent-policy-file.

The list of traces includes one of the following:

Depending on how you opened the Traces window, some information is displayed in the header and some information is displayed in the table. By default, traces are displayed in descending order, according to the latency value.

To filter the list of traces

You can filter the list the same way you did when filtering the list of business transactions.

Diagnostics data of traces

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

In the Traces window, an apparent discrepancy sometimes is displayed in the collected data. The list of traces is updated immediately when the agent sends a trace. Likewise, in the header of the Traces window, the Captured Count value is updated immediately. Metrics that are shared with the Business Transactions window or the Application Server window — Availability, Business Transaction Count, Latency Violations, Errors Count, Avg Latency, Max Latency — are recalculated every five minutes. The differences in the update can result in an apparent discrepancy, where, for example, the Max Latency value in the header is less than the value for a trace that is displayed in the table.

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.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*