πŸ“‘ Live Telemetry

Every LLM and MCP request routed through the gateway β€” raw, unfiltered. Click πŸ” on any row to open its full execution trace.

πŸ” Trace Explorer
πŸ“– How to read this table
Span Type β€” what kind of operation: mcp_tool = called a tool, llm_call = called a language model. Multiple rows with the same Trace ID = one conversation turn.
Trace ID β€” groups all steps of one conversation together. Click πŸ” on any row that has one to see the full execution path.
Destination β€” where the request was sent. mcp:// = tool call, http:// = LLM or internal.
Latency β€” wall-clock time from when the request was sent to when the response came back, including network.
Tokens β€” how many words (roughly) were sent to and returned from the LLM. Higher = more expensive.
Cost β€” estimated USD spend for this single call based on the model's pricing. Zero for MCP/tool calls.
Time Span Type ? Agent Destination Latency ? Tokens ? Cost ? Status Trace ?
Loading…