Sessions and traces

The gateway names each session in this order:

• The X-Intertrace-Session-Id header, when your client sends one. This is the most reliable option.
• The provider's own conversation id, when there is one.
• A conversation inferred from the opening messages.
• A 30-minute window, only for requests with no body.

A session ends after 15 minutes idle. Counts, risk and its reasons, and whole-session detections are kept per session. A session with status blocked was contained by an operator.

A turn is one request and everything it caused: the model call, tool decisions, MCP calls and the app's run of a proposed tool call are grouped together, so a conversation reads as the steps a person would recognize.

The session page opens on the trace viewer: the conversation's turns as a step tree on one timeline, with each step's decision, input and output, and what it touched in the activity ledger. Other views of the session stay available as tabs. Traces sent from SDKs or OpenTelemetry show in the same viewer.

Links can point at a turn or a step (?turn=, ?step=) or a single gateway event (?event=). A /dashboard/traces/<id> link for an id that names a conversation opens that conversation.