CloudflareDaniel WalshAnnouncement
Introducing Cloudflare Traces: follow requests through our entire platform
Summary
Cloudflare Traces, in open beta, extends tracing beyond Workers to the full request path, capturing spans for security, transformations, cache, routing, Workers, and origin handling in one timeline. Users set a baseline sampling rate and use Trace Rules to override it for specific traffic, enabling targeted debugging without increasing volume across the domain. The feature accepts and forwards W3C traceparent headers for distributed tracing and exports spans via OTLP to any compatible backend, with no instrumentation required. It reveals why a request was blocked, which rule acted, whether the URL was rewritten, and where time was spent between cache, origin, and the application. Pricing, effective December 1, 2026, is based on ingestion and retention: free tier 0.5 GB daily with 7-day retention, paid plans 50 GB ingestion and up to 365-day retention.
Context
Cloudflare Traces extends automatic tracing beyond Workers to the entire request path, capturing spans for security rules, transformations, cache decisions, routing, Worker execution, and origin handling in a single timeline, using OpenTelemetry and W3C trace context propagation.
Approach / What changed
Enable tracing per domain from the Cloudflare dashboard, API, or Terraform. Set a baseline sampling rate and use Trace Rules to override it for specific traffic using the Cloudflare Rules language. Accept and forward W3C traceparent headers for distributed tracing. Export spans via OpenTelemetry Protocol (OTLP) to any compatible observability backend.
Takeaways
Cloudflare Traces automatically captures spans for security rules, transformations, cache decisions, routing, Worker execution, and origin handling without additional instrumentation.
Trace Rules allow overriding the baseline sampling rate for specific traffic using the Cloudflare Rules language, enabling targeted debugging without increasing volume across the domain.
Pricing is based on data ingestion and retention: free tier includes 0.5 GB daily ingestion with 7-day retention, paid plans offer 50 GB ingestion and up to 365-day retention.
FAQ
How do I control which requests are traced?
Set a baseline sampling rate per domain, then use Trace Rules to override it for matching traffic based on hostname, source IP, request header, path, method, geography, or combinations, using the Cloudflare Rules language.
Can I export traces to my own observability platform?
Yes, configure an account-level OTLP destination and choose which domains send traces to it. Cloudflare exports spans via OpenTelemetry Protocol, making them portable across observability tools.
Does Cloudflare Traces support distributed tracing across my stack?
Yes, Cloudflare Traces accepts and forwards W3C traceparent headers, allowing Cloudflare spans to join a trace that began before the request and continue through your origin and other instrumented services.
Source and freshness
- Source
- blog.cloudflare.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.