# Sessions Read the sessions you've captured — timeline, filters, replays, and conversation context. This page is about reading sessions *in the dashboard*. For how to capture and enrich sessions from your code, see [Sessions (instrumentation)](/docs/instrument/sessions.md). The **Sessions** page is where most analysis starts. Every session is one user journey through your agent — a conversation with all its LLM calls, tool calls, events, and feedback in one place. ## What it is A **session** is a logical conversation thread, identified by a session ID you control. Inside one session you see: - **Messages** — every user turn and agent reply. - **Tool calls** — function calls the agent made (with arguments and results). - **LLM spans** — each model call with its prompt, completion, token usage, and latency. - **Events** — custom events you emitted from your code. - **Feedback** — thumbs-up/thumbs-down signals captured for individual responses. ## How it's populated Sessions are built from spans the SDK emits with a `brizz.session.id`. The session ID is whatever you set in `start_session` / `withSessionId` — usually a conversation ID from your database. See [Sessions (instrumentation)](/docs/instrument/sessions.md) for the SDK calls. ## How to read it in the dashboard The Sessions page has two halves: - **Session list (left).** Sortable by start time, session id, duration, or total tokens. Filter chips at the top apply common views. - **Session detail (right).** Click any session to open the timeline, conversation, and metadata panes. ### Filter chips - **Negative Sessions** / **Positive Sessions** — only sessions containing matching feedback events. These appear once the corresponding system-event mappings exist; see [User feedback](/docs/instrument/user-feedback.md). - **Low User Satisfaction** — sessions Brizz scored as negatively received. ### Search and filter Filter sessions by `user_id`, `service_name`, custom session properties, time range, or free-text search across conversation content. Combine filters; combinations URL-encode so you can share a link. If you report your own scores with [`record_metric`](/docs/instrument/record-metric.md), each one becomes a numeric filter here too — "show me every session my judge scored below 0.6". See [External metrics](/docs/platform/external-metrics.md). If your agent is built out of named skills, a **Skill** filter narrows to the sessions that activated a given skill — useful for asking whether one skill is behind a spike in problems. The same filter exists on [Issues](/docs/platform/issues.md). It only offers values once Brizz has seen skill activity for the service. ### Export conversations The **Export conversations** action exports the sessions matching your current filters as Markdown — a fast way to hand a set of real conversations to a teammate or to an AI coding agent. - **Format** — one Markdown file per conversation bundled in a ZIP, or every conversation combined into a single Markdown file. - **Limit** — up to 1000 conversations, taken in the order the list is currently sorted (newest first unless you've changed the sort). - **Include events**, **Include tool calls**, **Include session metadata** — metadata adds cost, tokens, properties, and labels to each file. The session title is always included. - **Compact long fields** — truncates long messages, tool inputs and results, errors, and event bodies over 4000 characters so the files stay readable. On by default. The export honours the filters you already have applied, so narrow the list first and export second. ### Session detail - **Conversation pane** — the human-readable transcript: user → agent turns, tool calls inlined. - **Timeline pane** — the session's activity as a graph of turns, tool calls, and agent steps rather than a row per raw span. Hover a row for its timing; activate it to expand or navigate into the detail. - **Metadata pane** — the session properties you set (user, plan, feature, etc.) plus inferred attributes. - **Metrics panel** — the metrics scored for this session, both Brizz's own and any [external metrics](/docs/platform/external-metrics.md) you reported. Click one for its gauge, comment, and attributes. - **Replay badge** — if you've configured a session-replay provider (FullStory, Mixpanel Session Replay, LogRocket), a one-click deep link to the recording appears here. - **External link badges** — any links your code attached with `add_external_link` / `addExternalLink` (a Datadog trace, Sentry issue, dashboard, …) show up here as one-click badges. See [External links](/docs/instrument/external-links.md). ## How to act on it 1. **Use the conversation pane first, the timeline second.** The transcript tells you what happened; the timeline tells you *why* — open it only when the transcript looks wrong. 2. **Filter by feedback to find the worst sessions.** Negative-feedback sessions are the highest-signal training set you have. 3. **Save filters you use repeatedly.** "Last 24h, errors, service = checkout-agent" should be one click, not three. 4. **Cross-reference with Issues.** When a session belongs to an open issue, the issue badge appears on it — useful when triaging a single complaint to the broader pattern. 5. **Share links liberally.** Session URLs are stable; paste them in PR descriptions, Slack threads, and bug reports. ## See also - [Sessions (instrumentation)](/docs/instrument/sessions.md) — how to capture and enrich sessions from your code. - [User feedback](/docs/instrument/user-feedback.md) — what makes the negative/positive filter chips light up. - [Issues](/docs/platform/issues.md) — the rollup of repeated problems across sessions. - [Session review](/docs/platform/session-review.md) — queue the sessions a human should read, by rule. - [Users](/docs/platform/users.md) — per-user rollups of the people behind these sessions. - [External metrics](/docs/platform/external-metrics.md) — filter and slice sessions by scores your own system produced. - [AI assistant](/docs/platform/ai-assistant.md) — ask about these sessions in natural language. - [Custom dashboards](/docs/platform/custom-dashboards.md) — build your own boards of [custom charts](/docs/platform/custom-charts.md) that aggregate the session data on this page.