The Sessions page organizes multiple execution records by session ID. This helps you view multi-turn interactions and continue to analyze the agents and execution steps from the content of a specific turn.
Prerequisites
-
The data contains valid session IDs, and all turns of the same business session use a consistent identifier.
-
The related trajectories have been processed.
-
The query time range covers the interactions that you want to view.
Data without session IDs is not automatically grouped into sessions based on usernames, time proximity, or message content.
Find a session
-
Open the destination SessionStore and select Sessions.
-
Set the time range.
-
Enter query conditions and click Search & Analyze, or use the filter panel and click Search.
-
In the Session List, open the destination session.
Example of a query by session ID:
session_id:"demo-session-001"Example of finding the session to which a trace ID belongs:
trace_id:"demo-trace-001"Replace the example identifiers with actual values. The list also supports conditions such as agent, model, tool, duration, and inputs and outputs. For more information about how to combine conditions and the prerequisites for semantic matching, see Query a single trajectory.
Note: The filter conditions in the session list are used to filter matching session records. After you open the details, the associated records are loaded by session ID within the same time window, and the details are not limited to the specific tool or keyword that is matched by the list conditions. Therefore, the details may contain more content than the records that are matched in the list.
View multi-turn interactions
-
In the Session Content section, select Formatted to view the interaction content in a readable format.
-
Use Compact List to quickly locate records, or select Expand All Details to read more content.
-
Select a record to view the linked agent topology on the right.
-
Click a topology node or the corresponding trajectory details entry to go to the next level of details and view the execution steps and step details.
-
In the trajectory details, use the directory or the previous and next navigation to switch to other trajectories.
Raw Trajectory Records displays the processed records that are associated with the session, not the raw logs before collection. To check the collected fields, switch to the Raw Data page of the SessionStore.
You can also switch to Log View on the Sessions page to check processed records one by one. After you switch, check the time range and query conditions. Log View is not a session list that is aggregated by session ID, and the number of records may differ.
Understand summaries and statistics
|
Page information |
Correct interpretation |
|
Session input and output summary |
Used to preview the content of earlier interactions within the current range. It is not necessarily the final answer of the entire session. |
|
Trajectory records |
The number of trajectory records within the current range. It is not equivalent to the number of user question-and-answer turns or the number of unique traces. |
|
Session duration |
The span between the start and end of the currently loaded records. It is not equivalent to the actual model computation time and does not necessarily cover the complete lifecycle of the session. |
|
Tokens and other totals |
Calculated from the currently available records. Multiple snapshots, missing data, and different statistical ranges may affect the totals. Do not directly use these values as the basis for settlement. |
|
Incomplete summary or truncation message |
Limited by the loading range or quantity of this query. You cannot conclude that the business has only these records. |
The current session summary and details have a loading limit of up to 1,000 records. If an incomplete message appears, narrow the time range or check the data by time period. Do not treat the current page as a complete session archive.
A session may span a long period of time. If the earliest or last turns are missing, check the time range first, and then check the collection and processing. Do not directly conclude that records are lost.
Copy records and open in a new window
Copy the current records
Copy All Raw Trajectory Records copies only the session records that are currently loaded. It does not automatically query data that is not loaded, and it is not an export feature for the entire SessionStore.
Before you copy the records, check whether the content contains personal information, business data, or model prompts, and anonymize the content as required by your organization.
Open a trajectory in a new window
If the trajectory details in a session provide Open in New Window, you can open the current trajectory separately for comparative analysis.
The new window mainly retains the destination SessionStore, the trajectory ID, and the corresponding absolute time range. It does not guarantee that manually written queries, all filters, the current page number, or the selected agent or step are carried over, and it does not pin the processing version.
Note: Copying the URL of the window does not automatically grant access permissions. The recipient must still log on and have the required resource permissions. The URL is also not an immutable link to a historical snapshot. Data updates, expiration, or permission changes may affect the result when the URL is opened later. No general operation is currently available to share the complete query state.