Cloudflare Adds Agent Tracing, with Truncation Limits and Uneven Payload Defaults

7.2 relevance

Cloudflare agent tracing is directly relevant to observability and agent orchestration.

AI/ML infoq.com

Answer the board on AI readiness

Arrive with evidence, not opinion. See how your foundation benchmarks against your peers, get a clear read, and leave with a ranked place to start.

Why It Matters

For platform engineers building multi-agent systems on serverless infrastructure, this fills a critical observability gap where an agent can return HTTP 200 while silently failing on tool selection or context, but the uneven privacy defaults and truncation limits require careful configuration before production use.

Key Takeaways

Audit your agent harness (Think vs Flue) and set storeMessages/storeTools or content:false explicitly to avoid leaking PII or secrets through payload recording defaults.

Cloudflare Adds Agent Tracing, with Truncation Limits and Uneven Payload Defaults

Summary

Cloudflare launched agent tracing, the first component of Cloudflare Agents, adding agent-level spans to existing Workers infrastructure tracing. The feature captures invocations, model calls, tool execution, and approvals in a waterfall view, with subagent work nested under parent operations. However, payload recording defaults differ between Think (opt-in) and Flue (opt-out), and traces are explicitly not a lossless record, with truncation limits on long messages and no image support in session replay.

Author

Steef-Jan Wiggers