After an agent chooses a suboptimal solution to a coding problem, the engineering team reviews the traces. The logs show every tool call and its parameters in detail, but contain no record of the agent's reasoning process — why it chose one approach over alternatives it must have considered. What observability gap does this represent?
Select an answer to reveal the explanation.
Short Explanation
You're missing the why layer. The logs show every tool call, but they don't capture the agent's reasoning trace, so you can't explain why it chose that approach. That reasoning is what turns a trace into a diagnosable incident.
Full Explanation
Complete agent observability has two distinct layers: action telemetry and reasoning telemetry. Action telemetry covers what tools were called, with what parameters, at what time, and what results were returned; that is what the team's current logging captures. Reasoning telemetry covers why those tools were called, including the agent's chain-of-thought, the alternatives it considered and rejected, and the confidence signals that drove its decision. Without the reasoning layer, post-incident analysis can describe the sequence of events but cannot explain the root cause of a poor decision.
For agents that use models capable of chain-of-thought reasoning, the reasoning trace is typically available in the model's response before the final action or tool call. Capturing that trace alongside the corresponding action lets engineers see that the agent chose one approach because it estimated another was simpler, but it was wrong about an assumption, rather than only seeing that the agent called a tool.
The missing available-tool-list explanation is a configuration artifact useful for debugging tool availability issues, not for understanding why the agent made a specific decision. Knowing what tools were available does not explain which one was chosen.
The missing model-version explanation is important for reproducibility and regression testing, but it does not help explain the reasoning behind a specific decision in the current run. The same model version can make different decisions in different contexts.
The wrong-format explanation would manifest as log parse errors or missing log entries, not as logs that are present but lack reasoning content. The scenario specifies that logs are present and contain tool details but are missing reasoning.
Reasoning traces alongside action telemetry are the complete observability picture for agentic systems.