Introducing Cloudflare Traces: follow requests through our entire platform

Cloudflare has introduced Cloudflare Traces in open beta, expanding automatic request tracing from Workers to supported operations across the full Cloudflare request path, including security rules, transformations, routing, caching, Worker execution, and origin handling. The service creates OpenTelemetry-compatible spans automatically without additional instrumentation, allowing users to inspect request timelines in the Cloudflare dashboard, control collection through baseline sampling and targeted Trace Rules, and trace selected traffic by properties such as headers, paths, IP addresses, or geography. It supports W3C traceparent context propagation so Cloudflare activity can connect with distributed traces from origins, external services, and applications, while OTLP export enables spans to be sent to compatible observability platforms. Cloudflare also highlights integration with its Observability MCP server for AI-assisted production debugging. Pricing will shift to a unified observability model on December 1, 2026, based on data ingestion and retention rather than span counts, and planned additions include broader instrumentation, authenticated propagation, on-demand tracing, expanded Workers OpenTelemetry APIs, and retention of up to 365 days.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.