Summary
Cloudflare has introduced agent tracing, enhancing existing Workers traces with detailed spans for agent invocations, model calls, tool runs, and approvals. While sessions can be replayed turn-by-turn, the documentation notes that traces are not lossless and payloads might be truncated, with default payload recording varying by framework. A significant change is that, starting October 1, 2026, every span will be considered a billable event.
Why It Matters
This article is crucial for a technical IT operations leader because it highlights a significant change in Cloudflare's tracing capabilities and billing model. Understanding the new agent tracing features allows leaders to better monitor and debug AI-driven applications deployed on Cloudflare Workers, ensuring operational stability and performance. More importantly, the impending change to a billable event per span from October 2026 necessitates immediate review of current and projected tracing usage to avoid unexpected cost increases. Leaders need to assess their payload recording defaults, optimize tracing granularity, and potentially adjust their budget and resource allocation strategies to manage these new operational and financial implications effectively.
