How to Trace and Analyze Events › Generating Cross-Process Transaction Traces

Generating Cross-Process Transaction Traces

As a system administrator, your responsibilities often include monitoring systems, addressing known issues, and then triaging these issues. You trace these systems issues using CA Introscope to find the components that caused them. To find these components, you construct filter criteria on the Transaction Trace screen. You then analyze the results to determine the problem.

The following illustration provides an overview of the basic trace processes:

This process has the following tasks:

1. Enable Cross Process Transaction Tracing.
2. Select Event Duration and Type filters.
3. Select CICS/IMS filters.
4. Select Trace Duration, agent filters, and start trace.
5. Narrow Trace by Excluding Front-End Elements.
6. Analyze Trace Results
7. Review or Adjust Results Components

Important! Running a transaction trace can have a negative impact on the performance of the monitored application.

Completing this process lets you understand which filters criteria to select to find the problematic components and how to analyze the results.