Hitmap
Hitmap is a menu that shows the response time distribution of completed transactions for the period you choose. Unlike the Hitmap widget on the Overview Dashboard and the AI Agent Main Dashboard, which shows only the 10 minutes up to the query time, it lets you specify a date and period to find ranges where slow transactions or errors are concentrated. Drag a range you found to analyze its transactions right away in the LLM trace details.
In the left sidebar, click Analysis > Hitmap.
Screen layout
| Area | Description |
|---|---|
| Option bar | Set the query conditions with Time Selection, Application, and the query button. |
| Hitmap Transaction | Shows the response time distribution of transactions completed during the query period. |
Querying
-
In Time Selection, specify the query period.
-
If a previously selected time (including one selected on another screen) remains in the browser, the menu opens with that time. Otherwise, today from 00:00 to 24:00 is selected.
-
Click the period length shown next to the query period (e.g., 1 day) to choose from a list: last 5 minutes, last 10 minutes, last 1 hour, last 7 days, last 14 days, or a single day (00 ~ 24h) for today, yesterday, or 7 days ago.
-
Real-time queries are not supported.
-
-
In Application, select the query targets. You can select applications individually, or change the display basis to By type or By server to select them in groups. If you select nothing, all applications are queried.
-
Click the query button (magnifier icon) to the right of Application. When you first open the menu, only an empty chart is shown; data appears only after you click the query button.
Reading the chart
The Hitmap Transaction chart places the transaction end time on the horizontal axis and the response time (elapsed time) on the vertical axis, and shows the number of transactions in each cell by color. The higher the cell, the slower the transactions.
-
Normal transactions are shown in blue, and the more transactions a cell contains, the darker the blue.
-
A cell with even one error is shown in an error color, which changes from yellow to orange to red as the number of errors in the cell increases.
The tools at the top right of the chart are as follows.
| Tool | Description |
|---|---|
| Count | Shows the number of normal transactions and error transactions in the query period, in that order. |
| Y-axis Auto | When on, the Y-axis maximum is reset to 5 seconds each time data is loaded, and widened one step at a time up to 80 seconds if transactions are concentrated in the upper cells. |
| Error | When on, only error transactions are shown. |
| Up/down arrows | Change the Y-axis maximum one step at a time among 5, 10, 20, 40, and 80 seconds. Changing it with the arrows turns off Y-axis Auto. |
| Left/right arrows | Move to the previous or next range of the same length as the query period and query again. The end of the next range does not go beyond the current time if the query period is 1 hour or shorter, or beyond 24:00 today if it is longer than 1 hour. |
Range analysis
Drag an area in the chart to open the list of transactions in that area in a new LLM trace details window. The top of the window shows "Trace analysis: N items found."
-
The dragged time range and response time range are used as the query conditions as is.
-
If you drag while Error is on, only error transactions are queried.
-
If you queried with applications selected individually in Application, only the transactions of those applications are queried.
-
Querying again or moving the range with the left/right arrows clears the previously dragged selection.
If you drag while querying with By type or By server selected, the window opens based on the entire project without the application condition. In this case, the list may contain more transactions than you saw in the chart.
The LLM trace details window shows the list of transactions in the range, and selecting a transaction in the list opens its details on the right. The details consist of the Record Summary, Table View, and Trajectory View tabs. For the contents of each tab, see LLM API Analysis. For the execution flow of a trajectory, see Trajectory View and Stop.
Reference: Difference from the APM Hitmap
The Hitmap in AI Agent Observability provides only the Hitmap Transaction chart. It does not include the application list and transaction list widgets or the AI analysis found on the APM Hitmap screen; transaction analysis is done in the LLM trace details opened by dragging.