Topic starter
18/08/2026 2:32 pm
TL;DR: Structured production traces become useful when they capture model calls, tool use, approvals, and infrastructure context together, according to Braintrust. Agent governance then depends on whether those records can reconstruct actions and authority boundaries after deployment.
Editorial analysis by NHI Mgmt Group, based on content published by Braintrust: “Trace and improve Cloudflare Agents”.
Key questions
Q: Why do production traces matter for governance in agentic systems?
A: Production traces matter because they turn agent behaviour into evidence.
Q: How do teams know whether agent handoff tracing is actually working in production?
A: Look for explicit evidence at the boundary.
Q: What breaks when agent runs are not traced in production?
A: When agent runs are not traced, teams lose the ability to reconstruct which model call, tool invocation, or approval led to a bad outcome.
Practitioner guidance
- Instrument agents for traceable approvals Capture approvals, tool invocations, and subagent steps as structured spans so each externally meaningful action can be reviewed after execution.
- Store production traces as evaluation inputs Keep representative traces from live workloads and reuse them to compare models, prompts, and tool changes before broader rollout.
- Separate behavioural evidence from usage metrics Review the sequence of actions, not just token counts or latency, when deciding whether an agent stayed inside its authority boundary.
Bottom line: Agent tracing becomes materially useful when it records the sequence of model calls, tool use, approvals, and infrastructure context in one place.
Glossary terms: Agent Trace, Production Evaluations, Tool Call Event, Approval Boundaries
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 5 hours ago by NHI Mgmt Group
18/08/2026 3:19 pm
Agent traces are becoming a governance record, not just observability data. Once model calls, tool use, approvals, and infrastructure context sit in one timeline, the trace can support review, accountability, and incident reconstruction. That changes the status of telemetry from operational convenience to evidence. Teams should treat trace retention and queryability as part of the control design.
A question worth separating out:
Q: Should organisations treat agent traces as audit evidence or just telemetry?
A: Organisations should treat agent traces as audit evidence when those traces are tied to approvals, access decisions, or customer-facing actions. Telemetry alone is not enough. Evidence becomes useful only when it can prove what happened, who or what acted, and under what authority.
👉 Read our full editorial: Cloudflare agent tracing clarifies production evaluation for IAM teams