Some Transactions Do Not Appear in the Transaction Trace Viewer

Symptom:

Some frontend or backend transactions or do not appear in the Transaction Trace viewer.

Reason:

The following may cause transactions not to appear:

The transaction trace may have been created to include or exclude backend transactions.
A transaction trace may have been created and the Trace All Supported Agents option was not selected.
Trace selected agents option and CA APM Cross-Enterprise was not selected for backend transactions.
The frontend agent has not been selected for frontend transactions.
The transaction trace may have been created with inapplicable criteria selected.

Solution:

Solutions follow:

Verify that you have selected the appropriate criteria.
Note: For more information about how to create a transaction trace to include frontend or backend transactions, see Understanding how backend trace options are used in frontend traces.
To determine if this 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 will confirm if there is a filter specific issue.

Transactions do not appear in the Transaction Trace Viewer:

If frontend 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 web service, CTG tracer, or WebSphere MQ live metric data for respective frontend Agents in Introscope Investigator tree.
- For the CTG tracer, you can see the metrics under the CTGTracer node.
- For the web services tracer, you can see metrics under WebServices node.
- For the MQ tracer, you can see metrics under WebSphereMQ node.
If frontend and backend traces are not correlated in the Transaction Trace Viewer the backend trace corresponding to the selected frontend trace may not have arrived yet. Reselect the trace after a short delay to refresh the display. If it still is not correlating, it may be due to these issues:
- The antiflood threshold is not set to low value. Antiflood threshold will limit the number of transactions sent to the Enterprise Manager. The default recommended antiflood threshold value is 200 transaction traces per 15 seconds. If you set low value for antiflood threshold, many traces are discarded before they are sent to the Enterprise Manager and hence likelihood of correlation will decrease.
- If it is a large volume of transactions, you can start new transaction trace window with smaller duration or proper backend filter setting to increase the chance of retention of transaction of interest.