Sessions
A session groups related traces into a single thread — typically a multi-turn conversation. Instead of reading individual requests in isolation, you can follow the entire exchange in order and see aggregated metrics for the whole session.
Open it from Sessions in the left nav. Traces join a session when they're sent with the same sessionId — set it when you instrument your app (see Sending Data In).
The sessions table
Each session shows:
- Session ID and the users involved
- Trace count — how many traces are in the thread
- Duration — span from first to last trace
- Total cost and tokens across the session
- Aggregated scores — averaged or distributed across the session's traces
Filter by timestamp and environment, search by session ID or user ID, and sort by creation time, trace count, duration, cost, or tokens.
Session detail
Open a session to see its member traces in order, the participating users, the tag distribution, and rolled-up cost/token totals. From there you can drill into any individual trace to inspect its observation tree.
When to use sessions
- Debugging conversations — follow how a chat evolved across turns to find where it went wrong.
- Conversation-level cost — see what a full conversation cost, not just one turn.
- Conversation-level evaluation — assess quality across an entire exchange (pairs well with evaluations).
Next steps
- Traces & Observations — drill into any trace in a session.
- Users — analyze activity per person.