Some Transactions Do Not Appear in the Transaction Trace Viewer

Symptom:

Some front-end or back-end transactions do not appear in the Transaction Trace viewer.

Solution:

The following reasons can cause transactions not to appear:

The transaction trace have been created to include or exclude back-end transactions.
A transaction trace have been created, and the Trace All Supported Agents option was not selected.
The Trace selected Agents option and Cross-Enterprise APM were not selected for back-end transactions.
The front-end agent has not been selected for front-end transactions.
The transaction trace have been created with inapplicable criteria selected.

Solutions follow:

Verify that you have selected the appropriate criteria.
Note: For more information about how to create a transaction trace to include front-end or back-end transactions, see About Cross-Process Transaction Traces.
To determine if the criteria selection is the problem, clear all transaction trace options except for the User ID does not exist option. Selecting this option allows all traces to be delivered to the transaction trace session window. This test confirms if a filter-specific issue exists.

Transactions do not appear in the Transaction Trace Viewer:

If front-end transactions are not appearing in the Transaction Trace Viewer, verify that the transactions that invoke web services, CTG, or MQ traces are running.
You can verify the web service, CTG CA SYSVIEW tracer, or WebSphere MQ live metric data for respective front-end agents in the Investigator tree.
- For the CTG CA SYSVIEW tracer, you can see the metrics under the CTGTracer node.
- For the web services tracer, you can see metrics under the WebServices node.
- For the MQ tracer, you can see metrics under the WebSphereMQ node.
If front-end and back-end traces are not correlated, the back-end trace corresponding to the selected front-end trace has probably not arrived yet. After a short delay, refresh the display by reselecting the trace. If it still is not correlating, the following issues are possible:
- The antiflood threshold is not set to low value. Antiflood threshold limits the number of transactions that are sent to the Enterprise Manager. The recommended default antiflood threshold value is 200 transaction traces per 15 seconds. If you set a low value for the antiflood threshold, many traces are discarded before they are sent to the Enterprise Manager. The likelihood of correlation decreases.
- If the volume of transactions is large, you can start a new transaction trace window with a smaller duration or proper back-end filter setting. This specification increases the chance of retention of the transaction of interest.