Multiple transaction trace
Multi-transaction means the transaction involving a different agent or project. Multiple Transaction Trace is to trace calls between the application services registered in the WhaTap project.
Enabling the multi-transaction
To trace multi-transactions, set the mtrace_enabled option to true in Management > Agent CONFIG.. For more information about the agent configuration, see the following.
Checking the multi-transaction ID
To use the Multiple Transaction Trace menu, MTID (Multi Transaction ID) is required. Through the following procedure, you can find the MTID value.
-
In Analysis > Hitmap, drag the chart area.
-
The transaction information in the dragged chart area is displayed in the TX trace list below as follows.

-
If you select the trace with the
icon displayed, the Transaction information window appears.
-
In the Record summary tab, you can see the Multi transaction ID value.

-
The same Multi transaction ID is generated even if the transaction makes an external call. Even if projects are separated by service, all transactions between applications can be found through the initially issued Multi transaction ID. For more information about the detailed analysis of transaction trace through the Transaction information window, see the following.
-
If you select Multi transaction ID in the Transaction information window, the Multi transaction tab appears. The transactions and trace data are provided so that you can see various call relationships at a glance within or between systems, and identify where problems occurred for improvement.
Using the multi-transaction tracing feature
-
Go to Analysis > Multiple Transaction Trace.
-
Enter the MTID value found in the Transaction information window into the Search by MTID / CUSTID field.
-
Select the date and project you want to query.
-
Click the Apply button at the bottom of the screen.
- The Apply button becomes disabled in the following cases:
- When the same filter values (MTID/CUSTID, date, selected project) as the previous search are set.
- When none of the filter values (MTID/CUSTID, date, selected project) are entered.
- The Apply button becomes disabled in the following cases:
-
The right Chart tab displays a diagram and a table that allow you to understand the call relationships of each transaction.
TipThe diagram and table areas are divided vertically, and you can adjust their ratio manually.
- Clicking the upward arrow makes the table occupy the entire area. However, if the diagram area was occupying the entire area, the diagram and table will split into equal halves.
- Clicking the downward arrow makes the chart (diagram) area occupy the entire area. However, if the table area was occupying the entire area, the diagram and table will split into equal halves.
Chart
Chart provides a fast and clear view of the call relationships between transactions.
You can check the individual execution times of transaction services that share the same Multi transaction ID.
The elapsed time displayed at the top of each transaction node (
Time Bar) allows you to understand the call flow between transactions.

You can freely move, zoom in, or zoom out of the chart with your mouse.
- Drag within the chart area to move it.
- Scroll within the chart area to move vertically or horizontally.
- Vertical scroll: move up/down
- Horizontal scroll: move left/right
- Hold
Ctrl+ scroll up/down to zoom in or out.- Pinch zoom on a touchpad is also supported.
When you select a transaction, only the connected nodes remain active, while all unrelated nodes are dimmed.
The Detail View button (
) at the bottom of the selected transaction becomes active.
Clicking it opens the Transaction information window, where you can view detailed transaction information.
For more details on analyzing transaction traces using the Transaction information window, refer to the following document: Transaction Info.
-
Zoom In
-
Zoom Out
-
Fit to Screen: Display all nodes to fit the visible area.
-
Reset Zoom: Restore the initial chart zoom and position.
-
Chart View Settings: Show or hide chart elements.
- More information: Show/hide application name, project info, IP, status code.
- Database / External: Display other database connections or external HTTP calls as nodes in the chart.
Table
In the Table tab, you can see information for each transaction included in a multi-transaction in the table format.
If you select each transaction, the Transaction information window for the selected transaction appears, similar to selecting a node on the Chart tab. The transaction trace allows you to see the transaction details. For more information about the detailed analysis of transaction trace through the Transaction information window, see the following.
Column Settings: You can edit the columns in the table.
Tree
In the Tree tab, you can see each transaction and its trace details. The transactions within the overall transaction time or start times and step times of each trace to provide transaction call relationships in a tree format.
-
Single-line View: You can arrange the tree format at intervals by displaying the texts displayed in the execution data for each section in a single line.
-
Multi-line View: All the texts displayed in the execution data for each section, appear by wrapping words.
-
Longest Path: The longest route can appear.
-
Show Time Bar: The elapsed times are displayed in a bar chart.
-
Show Time: The timestamps, gaps, and elapsed times for each segment are displayed in text.
-
8 seconds or more: Excessive delay state is distinguished in red.
-
Between 3 and 8 seconds: Delay state is distinguished in orange.
-
Less than 3 seconds: Normal state is distinguished in blue.
NoteIn case of start and step times, the time differences caused by the transaction call environment are corrected on the screen through traces and mappings in the parent transactions. Accordingly, there may be differences from the actual time data.
-
-
Hide Time: The time is hidden.
If you select button or
button, you can see the summary window such as HTTP call statistics and Active stack.
To search SQL variables and HTTP queries, add the following options to the agent settings.
-
For agent settings related to recording SQL parameters, see the following.
-
For agent settings related to recording the HTTP parameters, see the following.
# SQL parameter lookup option: If the option is applied, SQL parameters are collected after being encrypted.
profile_sql_param_enabled=true
// HTTP parameter lookup option: If the option is applied, HTTP query parameters are collected after being encrypted.
profile_http_parameter_enabled=true