Cloudflare has announced Cloudflare Traces, a new observability feature that follows a single request through every stage of its platform. According to the announcement, Traces shows how a request moves through security rules, transformations, cache, routing, Workers, and your origin, then follows it across services running anywhere in your stack. For developers, this means you no longer need to stitch together logs from separate systems to understand what happened to a request.
The concrete capabilities described include:
- End-to-end tracing: follow a request through security rules, transformations, cache, routing, Workers, and your origin in one view.
- Cross-service visibility: traces continue across services running anywhere in your stack, rather than stopping at Cloudflare’s edge.
- Single request context: see the path and decisions applied to an individual request, not just aggregate metrics.
- Platform-wide coverage: the feature is designed to work across Cloudflare’s entire platform as described in the announcement.
Because the announcement does not list CLI commands, APIs, or version numbers, developers should treat this as a capability overview rather than an API reference. The key shift is architectural: request flow becomes a first-class, traceable object that spans edge logic and origin services.
Why this matters to developers: debugging distributed systems often means correlating logs, metrics, and traces from multiple providers. Cloudflare Traces aims to reduce that friction by placing request-level visibility directly in the platform where security, caching, and compute already run. That can shorten incident response, clarify why a request was blocked, cached, transformed, or routed in a certain way, and make performance issues easier to attribute to a specific stage. For teams using Cloudflare Workers and other platform features, the promise is a more coherent debugging workflow without leaving Cloudflare’s tooling.