We are the Frontier
U.S.

Cloudflare Launched Open Beta for Traces

The service bridges visibility gaps between client and application by proxying traffic data to observability tools.

Updated on Oct. 10, 2026 in Data Centers

Bold flat-color editorial illustration in navy and cream, depicting a symbolic fiber optic connection to a central network node.
Cloudflare has introduced Traces, a new observability service that generates OpenTelemetry data by intercepting network traffic at the edge for distributed systems. AI Illustration. Upload story photo >

Live Poll

Do you prefer cloud pricing based on data usage over fixed per-feature subscription costs?

Cloudflare has launched an open beta for its new Traces service, which automatically generates OpenTelemetry spans for network security rules, cache decisions, and worker execution paths. The platform allows teams to propagate context using standard W3C traceparent headers while providing granular control over sampling.

Why it matters

By intercepting traffic at the edge, Cloudflare Traces provides visibility into distributed systems that previously lacked a unified connection between client requests and back-end application performance. This integration helps engineering teams debug complex routing and worker execution paths from a single proxy source.

The system supports a baseline 1% sampling rate, with custom rules allowing overrides based on specific paths, headers, or geographies. Paid plans offer 50GB of ingestion and 10GB-month of storage per billing cycle, compared to the free tier's 0.5GB daily ingestion limit.

The players

Cloudflare

A global provider of edge computing, security, and networking services that manages traffic for a significant portion of the internet.

The details

Cloudflare Traces generates OTLP (OpenTelemetry Protocol) spans—structured metadata representing the duration and path of a request—by intercepting traffic at the edge. Users configure an account-level OTLP destination to receive this data, while the platform's Observability MCP (Model Context Protocol) server allows automated coding agents to query these traces using a SQL API. This approach centralizes visibility into security rules, cache outcomes, and code execution without requiring manual instrumentation of every microservice.

Timeline

  1. August 2026: InfoQ reported on early agent-based tracing work.

  2. October 1, 2026: Spans transitioned to a billable event model.

  3. October 10, 2026: Cloudflare Traces entered open beta.

  4. December 1, 2026: New volume-based pricing model takes effect.

The Tech Race

Cloudflare is positioning its edge infrastructure as a primary observability source to compete with traditional application-level monitoring tools. This development aligns with the industry-wide move to standardize on OpenTelemetry for cross-platform data compatibility.

Engineers can immediately begin configuring OTLP destinations to monitor traffic without modifying application code. Usage under the new volume-based pricing structure will apply to all accounts starting December 1, 2026.

The takeaway

Cloudflare is effectively turning its edge proxy into an active observability participant, simplifying complex distributed debugging. Users should monitor the transition to volume-based billing on December 1, 2026, and track upcoming releases for support for Workers execution paths.

Further reading

For more background on how infrastructure manages traffic flow, visit the Data Centers section.

Source note: This article includes information reported by InfoQ.

Live Poll

Do you prefer cloud pricing based on data usage over fixed per-feature subscription costs?