Cloudflare has made Traces available in open beta, extending automatic tracing from Workers to the entire request path. Security rules, transformations, cache decisions, routing, Worker execution, and origin handling now appear as OpenTelemetry spans in a single request-level timeline, requiring no manual instrumentation.
Previously, a trace would show the client and then the application, leaving everything in between to be inferred from logs and configuration. Each supported step now arrives as a span with its timing, outcome, and attributes. The feature addresses questions developers commonly encounter: which security rule blocked a request and how long did evaluation take? Did a Transform Rule rewrite the URL before the application received it, and where did that happen relative to routing? Which Page Rule, Snippet, or Worker handled the request, and which route pattern matched? A cache miss example showed 527 milliseconds out of 539 total milliseconds went to fetching a response from the origin.
Alongside the open beta, Cloudflare introduced a pricing change that applies to Workers Tracing as well, shifting to a volume-based model. No specific pricing figures were disclosed. The move aims to give developers deeper visibility into the behavior of Cloudflare's proxy layer for debugging and performance analysis.