From Spans to Agent Scenario: Why We Added a GenAI View of the Trace
OpenAI
Proto Observability Platform has introduced a dedicated GenAI trace view with four modes: feed, step graph, call graph, and chat. Each mode answers a different question about agent behavior, from sequential execution to user-visible results. The design was driven by real defects in GenAI instrumentation, such as repeated context, hidden errors, and token counting issues.
The Proto Observability Platform added a GenAI view for traces, addressing the difficulty of reconstructing agent logic from a simple tree of spans. The view has four modes: a feed showing operations in chronological order with timing, a step graph that collapses repeated operations to reveal the agent's loop, a call graph that shows each individual invocation with its unique arguments and status, and a chat mode that reconstructs the user's conversation from potentially repeated message history. The developers encountered several real-world issues: full conversation histories were sent with each model call, leading to duplicates; transport spans could distort timing if summed naively; structured tool results might contain errors even when the operation status appeared successful, so the error model was separated from the display model; and token consumption could be cumulative or per-operation, requiring careful semantics detection before aggregation. The representation intentionally hides details not relevant to the question each mode answers, while raw attributes remain available for verification.
- Abbreviations
- GenAI = Generative Artificial Intelligence
- HTTP = Hypertext Transfer Protocol
- JSON = JavaScript Object Notation
- MCP = Model Context Protocol
- RPC = Remote Procedure Call
- SDK = Software Development Kit
Source: Habr — хаб ИИ —
original
