Transaction search
Home > Select Project > Application > Analysis > Transaction Search
In Transaction Search, you can view the statistics on the performance and execution status for each transaction for a specific period of time. You can view all transactions and their errors. The provided information allows you to see which transactions are busy and resource-consuming. The transactions are filtered in various ways depending on the transaction properties, making it useful for finding transactions with specific conditions.
Set the search time in the area, and then select search targets from the Container options. If you select , the search results appear in the table. If you select desired items from the result list in the area, the Transaction Info window appears. For the detailed information on the transaction trace analysis using the Transaction Info window, see the following.
-
To search for transactions in error, click Errors only and then select .
-
It is recommended to set the search time as short as possible because a response delay may occur depending on the search conditions.
Select Column
If you click Select column in the area, the column selection window appears as follows. Select desired columns.
Apply Filter
You can perform detailed search using filters in the Leader line 1 area. It supports data exploration using various search conditions. Multiple filters can also be applied. Specify desired filters and then select .
-
Some filters may not be supported depending on the product.
-
When applying multiple filters, to search by the Multi transaction ID filter, only the Transaction ID filter can be added.
Elapsed Time
Search is performed based on the transaction response time. Search by entering two values above and below the reference.
Error Message
Search is performed based on the transaction error message. In the default state, error-related columns may not be seen. Select a column to check.
Transactions in error are displayed in red.
HTTP Call Count
It searches the transactions in which the number of calls for external HTTP services is greater than or equal to the input value. For example images, 5 or more cases are viewed.
SQL Count
It searches the transactions in which the number of SQL executions per transaction is greater than or equal to the set input value. It is used to search for transactions that exceptionally call an excessive number of SQLs.
SQL Fetch Count
After execution of SQL, the transactions whose count is the input value or more based on the number of DB patches. It is used to search transactions that perform excessive data patching.
Transactions
Search is performed based on the transaction. The entered search string is compared for a search based on whether it is included or not (partial match).
Client IP
The transactions are searched based on the client IP. However, IP strings are searched using PREFIX comparison (forward match).
Domain
Transactions are retrieved based on the HTTP service domain (host:port). The search conditions must match the domain completely (full match).
UserAgent
Search transactions based on the user agent (partial match).
Referer
Search transactions based on the referer string.
Transaction ID
Search transactions based on their transaction ID (full match). For transaction IDs, the search indexes are created for searching at a high speed.
-
The transaction ID can be found in the Record summary tab of the Transaction information window. For more information, see the following.
-
If you are not using the latest version of the agent, a full scan may occur rather than using indexes.
Multi Transaction ID
Search transactions based on the multi-transaction ID (full match).
-
The multi-transaction ID can be found in the Record summary tab of the Transaction information window. For more information, see the following.
-
If you are not using the latest version of the agent, a full scan may occur rather than using indexes.
-
When searching with the Multi transaction ID filter applied, only the Transaction ID filter can be additionally applied.
WClientID
The client ID (wClientId
) is an ID given by the WhaTap agent to identify users. Transactions are searched based on this ID (full match). There is no separate index for searching.
WhaTap basically stores the client-related information.
Login ID
Search transactions based on the login ID.
Agents in their default settings do not collect login IDs. For more information about the login ID setting, see the following to add settings.
Downloading the searched results
The searched results can be downloaded as a CSV file according to the filter conditions set by the user.
-
Click to view the searched results.
-
Select .
-
Enter the maximum number of CSV lines. You can save the searched results as many lines as you enter.
-
Select Download to download the CSV file.
The CSV file name's format is profile_{pcode}
_YYMMDD
.csv.