What to know
- Traces extends automatic tracing beyond Workers.
- Supported stages include security, routing, cache and origin handling.
- A missing span needs to be distinguished from a stage that never ran.
A request history spanning more stages
Cloudflare introduced Traces in open beta on October 2. It extends tracing beyond Workers to supported security rules, transformations, cache decisions, routing and origin handling, with continuation through services elsewhere in the stack. The company links the design to OpenTelemetry and a longer-term effort to improve visibility across its platform.
The specific value is a connected history of a request. An operator may need to know whether a rule changed it, whether a cache served it and whether an origin received it. Separate product dashboards can each show a valid observation while leaving that sequence unclear. Tracing attempts to connect the stages rather than simply collect more aggregate counts.
Source: Cloudflare: Traces open beta
Analysis: Absence in a trace needs interpretation
A trace can reveal where work spent time, but it can only show what the instrumentation captured. A missing stage might mean the request did not reach it, or that the stage is unsupported, unsampled or incorrectly connected. Treating every blank as proof of non-execution could produce an inaccurate diagnosis.
Teams should therefore understand the trace’s coverage before relying on it during an incident. A controlled request with a known path can show which stages appear and how identifiers continue across services. The same trial can reveal whether a retry looks like a separate operation or remains connected to the original task. Those distinctions matter when a user sees one failure but the system performs several attempts behind the scenes.
Practical implications: Trace a case with a known answer
Engineers can evaluate the beta by sending requests whose expected cache, routing and origin behavior is already understood. They can then compare the visible trace with server records and timing measurements. The aim is to establish which questions the new view answers confidently and where an operator still needs another source.
Sensitive metadata deserves a defined collection policy. URLs, headers and attributes can reveal information beyond what is required for diagnosis, so access and redaction should follow the actual service’s needs. Cloudflare’s beta offers a wider view of request execution, while its announcement keeps supported coverage as an explicit condition. The useful outcome is an investigation that can connect a user-visible problem to the relevant decision in the path, with missing evidence identified instead of silently filled by assumption. That requires both instrumentation and an operator who understands what the trace represents.
Operators should also distinguish a slow request from a slow stage. A short span at the origin does not explain time spent before it. Comparing the complete user-visible interval with the recorded path can expose missing context.
Sources & further reading
Factual statements are grounded in the linked material. Interpretation and illustrative examples are Byte Watchr analysis. Vendor claims are identified as claims, rather than independent testing.
The event date records the source announcement or documented operation. The coverage edition groups recent developments and is separate from the publication date. Actual publication is recorded above.
Corrections policy · About this byline
