Transaction Map
Home > Select Project > Dashboard > Transaction map
The Transaction map chart displays the response times for each completed transaction in the distribution chart form. Same as the hitmap, you can find and analyze problems based on the distribution patterns. Hitmap displays the grouped transactions every 5 seconds, but Transaction map displays transactions individually.
How is it different from the hitmap analysis?
The hitmap uses the aggregated data to display the overall trend over a long-term period. On the other hand, the transaction map uses individual transactions to check the transaction distribution within a short-term period with no time constraints. It also differs in that it allows users to apply various filters to select only the desired transactions and observe their trends.
-
To analyze the distribution of the long-term, high-volume transactions, use the hitmap analysis (Analysis > Hitmap).
-
To do performance test, or analyze the transaction distribution within 1 to 5 minutes upon a failure, or check the transaction distribution without limiting the execution time, check the Transaction map.
-
For more information about Hitmap, see the following.
-
For more information about the analysis method of the HITMAP transaction chart, see the following.
-
If the user's PC time is set to earlier than the server time, or the difference between two times is 5 minutes or more, the data may not be displayed in the chart.
Analyzing a trace
If you drag the chart area of Transaction map, the Trace analysis window appears where you can check the transaction details. You can see the transaction list and the steps under each transaction at once.
After dragging the chart area, you can see up to 1,000 items in the Trace analysis window.
For more information about Trace analysis, see the following.
Changing the lookup criteria
Select the chart area of Transaction map and then the button at the upper left to change the data lookup criteria.
-
Elapsed time: The data is displayed based on the transaction execution time.
-
HTTP call time: The data is displayed based on the response time against the HTTP call.
-
SQL time: The data is displayed based on the SQL execution time.
-
CPU usage time: The data is displayed based on the CPU used time.
Filtering the searched results
In the chart area of Transaction map, you can distinguish the results by selecting Total, Error, and Read phrases in the upper right corner.
Total: Displays total transactions
Error: Only the transactions in which errors occurred, are displayed.
Read: The number of transactions read from the server is displayed.
For example, if you select an error and then drag a transaction on the chart, the Trace analysis window appears to display a list of erroneous transactions. To view all transactions, click Total.
Adjusting the Y-axis
-
You can easily change the maximum value of the Y-axis by selecting
or
on the upper left of the chart. You can also access the same function by pressing the up or down button on the keyboard.
For more information on how to use the
or
button or keyboard buttons depending on the Y-axis section, see the following:
-
The segment from 10 to 50 seconds is changed to the 10-second interval.
-
The segment from 50 to 300 seconds is changed to the 50-second interval.
-
For the segment of 300 or more seconds, it is changed to the 100-second interval.
-
-
You can change the maximum value of the Y-axis by directly entering it. Select
, enter a desired value, and then select Apply.
The maximum number of transactions (Limit) displayed on the chart in Transaction map is 2,000,000.
When you apply filters for a search, the Read value may be greater than the Total (number displayed on the screen).
Viewing the past data
Transaction map provides the real-time monitoring by default. By default, the data can be viewed in real time for 5 minutes. Click the green button in the time selector to select a desired lookup time.
To view the historical data, click in the time selector. It changes to period viewing mode and you can view the transaction data for up to 1hour. The chart data of Transaction map based on the date and time set by the user is refreshed.
You can stop the query at any time while searching the past data. _ To change the filters, first stop the query, and then change the filters. _ If you press the Search button again without changing the filters, it continues searching from where it was stopped.
To switch to the Realtime mode after a historical inquiry, click .
-
The range of the historical inquiries may differ depending on the transaction volume.
-
For more information on how to use the time selector, see the following.
Applying filters
In case of viewing the past data, you can filter out the data by applying filters.
-
When you click the Pause (
) button, the filter input box appears.
-
If you click the filter input box, the list of filters that can be selected appears as follows.
-
General filters
Item Description Login ID Viewing with the login ID of the user WClientID Searched by the unique identifier per client
※ Searching is performed by exact match.Transaction ID Unique ID per transaction
※ Searching is performed by exact match.Referer Searching is performed using the Referer (referring page address) delivered by a transaction request. Multi Transaction ID Unique ID that groups multiple transactions
※ Searching is performed by exact match.Custom TID Searching by the custom transaction ID Error(Class, Step, Message) Searching by error type, step, and message in transactions (partial match included) City Searching by the user's town for transactions Country/Region Searching by the user's country for transactions HTTP Method HTTP request method (GET, POST, etc)
※ Searching is performed by exact match.UserAgent Searching by browser or client information (user agent) for transaction requests -
STEP Filter
Step indicates the profile data collected while performing transactions. When dragging the hitmap, the sequential data displayed in Table View or Tree View by clicking a transaction in the transaction list is called Step.| 항목 | 설명 |
| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| DBC | Step that contains the method running while performing transactions |
| HTTPC | Step that contains the HTTP call |
| MESSAGE | Step that contains various texts while performing transactions |
| METHOD | Step that contains the method running while performing transactions |
| SQL | Step that contains executed queries |
| SQL_BIND | Data that does not exist actually but is included in the SQL step <br /> Step with which bind variables and substitution variables can be viewed during the SQL call <br />※ Searching is possible with the authority and decryption key to view sensitive information. |
| ALL | Step with which all the above steps can be searched <br /> ※ Searching is possible with the authority and decryption key to view sensitive information. | -
Number input filter
Item Description Elapsed time Total time taken for the transaction to be performed HTTP Call Time Response time for HTTP Requests HTTP Call Count Number of HTTP requests while performing transactions SQL time Total SQL execution time for transactions SQL Count Number of SQL queries executed for transactions Status Transaction status(e.g. Normal, Error, etc.)
-
-
Enter the desired values for filtering. For filtering, enter all values for the filter key, operators, and values. If there are any filters that have not been entered yet, searching is not possible.
-
Aftering entering all filters, click
.
It updates the filtered data in the Top 30 list and the Transaction map chart.
-
You can perform filtering by setting multiple conditions. Added conditions are applied based on
&&
. For example, if the transaction is/account/save/employee/seoul
and the elapsed time is more than 3 seconds, you can apply as follows:Transaction
=
/account/save/employee/seoul
Elapsed time (ms)
>=
3
Checking the agent
Checking the agent connection status
On the upper left of the screen, the right area of the time selector provides information that allows you to check the status of agents connected to the project. This allows you to immediately check whether the target application server is running.
-
Total: Number of all agents connected to the project
-
Active: Number of active agents
-
Inactive: Number of inactive agents
-
: Can display or hide inactive agents.
Agent-based monitoring
By default, the chart displays the metrics collected from all agents in charts and you can also view the data by agent. Select one or more agents under the time selector. The chart is updated with the transactions of the selected agent.
To select all agents again while one or more agents is selected, deselect them or click Total.
If there are numerous agents connected to the project, it is efficient to set the agent names to be short. For more information about the agent name setting, see the following.
Monitoring each classified agents
You can easily monitor multiple agents by categorizing them in Agent Settings.
-
Agent: Individual Agent
-
By kind: Group classified by the agent type (e.g. web server, database). Set it to
whatap.okind
. -
By server: Group categorized by the server (node). Set it to
whatap.onode
. -
Agent by kind: List of agents classified as
whatap.okind
. -
Agent by server: List of agents classified as
whatap.onode
.
For more information about the agent configuration, see the following.
Searching the agent
If the agents connected to the project are numerous and difficult to find, use the agent search function. If you click Search on the upper right of the screen, a box appears where you can enter a string.
The agents that match the entered string appear in the list. To filter the data in the dashboard based on the searched agents, click Select on the right of the text entry box.
To reset the selected agent entries, click Close on the right of the input field.
Checking the upper list
In the Top 30 section, the list of top 30 items with the highest transactions performed based on Transaction, Domain, IP, and Agent.
-
Transaction: Top 30 items, aggregated by the transaction URL
-
Domain: Top 30 items aggregated based on the Internet address specified in the address of the IP connected by the client
-
IP: Top 30 items, aggregated by the client IP address
-
Agent: Top 30 items aggregated by the agent included in the project
If you select each item from the list, the data is applied based on the item selected in the Transaction map chart. To select multiple items, hold down the Ctrl
(Windows/Linux) or CMD
(Mac) key and then click desired items.
You can move an item in the list of the Top 30 section by pressing the up or down arrow button on the keyboard.
Add custom IP address
When viewing the number of transactions executed based on IP in the TOP 30 section, the function is provided to check constantly by adding a specific IP address.
-
In the TOP 30 section, select IP.
-
Enter a specific IP address in the field at the top of the list.
-
Click
.
The specified IP address appears at the fixed top of the list.
To delete any added IP address, click .
Custom monitoring
It provides the feature to check only the selected items in the response time distribution chart by adding specific transactions, domains, and IPs to the Custom tab. This allows users to efficiently monitor and analyze specific problematic items.
-
Click the Custom tab.
-
Transaction or Domain, IP can be entered directly, selected from the Top 30 list, or searched.
-
Click the added item.
You can see the response time distribution for the selected items filtered in real time on the chart on the right.
To delete any added custom items, click .