06/Platform & Admin

Request tracing (Phoenix)

From a Request Logs row to its Phoenix trace: prompt, routing, masking and every upstream attempt.


Every chat request is exported to Arize Phoenix as an OpenTelemetry/OpenInference trace. The Phoenix link on a Request Logs row opens that request's trace.

root
The prompt the client sent and the final answer the user saw.
routing
Group, strategy, chosen member and masked links.
gateway.prepare
The request after system prompts, memory and guardrails.
masking
Which value became which placeholder, with GLiNER score or manual rule; the restore step shows what was put back into the answer.
LLM
For each attempt: real model, provider, node, the (masked) messages on the wire, raw answer, tokens and error.
agent / tool
MCP agent turns and tool calls nested in the same trace.
Phoenix also stores unmasked prompts. In production enable Phoenix authentication or set TRACING_CAPTURE_CONTENT=false to export metadata only.