What changed
On October 2, 2026 Cloudflare announced eight observability updates spanning logs, traces, analytics, alerts, dashboards and telemetry export. Cloudflare Traces is in open beta and records supported request-processing steps as spans, including security rules, transformations, cache decisions, routing, Workers and origin handling. A unified SQL API in beta provides one query surface across Cloudflare data, while Workers logs and OpenTelemetry traces can now appear in Custom Dashboards. Cloudflare is also replacing separate observability charging with a common ingestion-and-storage model beginning December 1, 2026.
Why it matters
Cloudflare sits in front of applications as well as running code and state for many of them, so failures often cross product boundaries. Request-level traces reduce the need to reconstruct a path from unrelated logs, and the SQL layer makes the same telemetry easier to query from software and agents. The pricing change matters operationally too: teams can model logs and traces under one ingestion/storage scheme rather than treating each signal as a separate product.
One trace can cross Cloudflare and the origin
Cloudflare Traces records supported edge processing as spans and can continue through Workers and downstream services using trace context. The aim is to show where a request spent time and which Cloudflare decisions affected it.
SQL becomes the common query surface
The new unified SQL API is intended to query logs, analytics, traces and security data through one dialect and authentication model. Cloudflare is also exposing observability data through its CLI and agent-oriented tooling.
Logs and traces get a common cost model
Beginning December 1, Cloudflare says logs and traces will share account-level ingestion and storage allowances. Paid and Enterprise plans include 50 GB of ingestion and 10 GB-month of storage per billing cycle, with additional usage priced by volume; unsampled security datasets have separate pricing.