Skip to main content
Open Monitoring to investigate an individual run. A trace shows how the agent turned a request into an outcome: its plan, research steps, tool calls, results, clarifications, approvals, and final artifact. Use a trace to answer practical questions:
  • Which agent, data scope, instruction build, and model handled the request?
  • What did the agent inspect or call in parallel?
  • Which tool, query, source, or approval delayed or failed the run?
  • Which evidence supported the final recommendation?
  • What should be changed to prevent the issue from recurring?
A run that delegated to sub-agents has one child run per sub-agent, each linked to the parent run and to the delegate call that launched it. The parent’s trace carries the records they returned; a child’s trace carries its own steps. For an incident investigation, traces connect the RCA narrative to the underlying logs, metrics, service tools, and database evidence rather than leaving a conclusion as an unexplained summary. After diagnosing a recurring issue, add an eval and improve the relevant instruction or agent configuration.