Cloudflare merges logs, traces and alerts into one platform

Cloudflare on October 2, 2026 announced eight updates that it says pull logs, traces, analytics, alerts, dashboards and data export into a single observability platform, alongside a new usage-based pricing model that takes effect on December 1, 2026.

What changed

In a blog post, Cloudflare said a new Logs home combines Workers Observability with Log Explorer, letting customers choose datasets including HTTP events, firewall events, Workers, Containers, R2 and AI Gateway and apply the same investigative tools to each. The company said support for querying across multiple datasets is coming soon.

Cloudflare Traces is launching in open beta, which the company said gives a request-level view of supported security rules, transformations, cache decisions, routing, Workers and origin handling. Customers can set a baseline sampling rate, use Trace Rules to capture specific traffic at a higher rate, search by Ray ID and inspect spans in the Cloudflare dashboard. Traces can be exported over OpenTelemetry, with W3C trace context propagation to accept and pass along context to an origin.

The company also announced a unified SQL API in beta for querying telemetry across Cloudflare products, usable from a new Cloudflare CLI called cf, through Cloudflare's Observability MCP server, or via a native binding inside Workers.

Alerts, analytics and dashboards

Notifications have been renamed Alerts, and Cloudflare said customers can now define custom alerts, in beta, on anything supported by the unified SQL API, including HTTP request logs, Workers events, Workers Analytics Engine datasets, analytics datasets, traces and security events. Conditions can be set by dataset or custom SQL, with threshold, anomaly or SLO options, and routed to incident management tools, chat platforms and webhooks. Webhooks are now available on all plans, the company said.

Domain analytics covering traffic, performance, security, cache, origin and DNS data are being brought into one view, with 30 days of retention on every plan. Custom Dashboards let teams combine analytics, Workers logs and traces, and security events in a single shared view.

Pricing and export changes

Cloudflare said Logpush, previously limited to Enterprise, is now available on all self-serve plans, and that Transformers, which applies SQL transformations before delivery, is generally available. Exports to Cloudflare destinations include 25 GB a month with additional usage at $0.03 per GB, exports to external destinations include 25 GB at $0.10 per GB, and Logpush Transformers include 1 GB at $0.04 per GB.

For logs and traces ingested and stored on Cloudflare, the company is moving to a single Observability subscription based on volume ingested and stored rather than event counts. Beginning December 1, 2026, the model applies across all plans and takes effect upon renewal for Enterprise customers, covering existing Developer Platform logs from Workers, Containers and AI Gateway as well as tracing data.

The Free plan includes 0.5 GB of ingestion per day with 7 days of retention and no additional usage. Paid and Enterprise plans include 50 GB of ingestion and 10 GB-month of storage per billing cycle, with retention of up to 1 year listed as coming soon, and additional usage at $0.25 per GB ingested and $0.10 per GB-month stored.

What Cloudflare says is next

The company listed longer retention of up to one year for logging and tracing data, further OpenTelemetry API support in Workers, and metrics export to OpenTelemetry-compatible destinations as upcoming work. It said customers will be notified before the pricing change takes effect.

Cloudflare framed the work as a response to customer feedback, writing that it hears customers say Cloudflare can feel like a black box, and argued that machine agents need queryable context to verify fixes.

What to do

• If you ingest or store observability data on Cloudflare, review the new unified Observability pricing before it applies on December 1, 2026; Cloudflare says it will notify customers before the change and points to its pricing documentation for details.
• Enterprise customers should note Cloudflare says the new pricing takes effect upon renewal.
• To try tracing, Cloudflare suggests setting a baseline sampling rate for continuous visibility and using Trace Rules to capture specific traffic at a higher rate during an investigation, targeting hostnames, paths, IP addresses or headers.
• For alerting, Cloudflare says to choose a dataset in the dashboard or define the condition with custom SQL, then select a threshold, anomaly or SLO, set the evaluation window and choose the destination.
• Cloudflare directs users to its Logpush documentation to get started with exports and to review complete export pricing.

Read the original from Cloudflare →