Cloudflare has announced eight observability updates that bring logs, traces, analytics, alerts, dashboards and exports into a shared platform. The practical prize is less detective work just to find the right place to start investigating an application problem. The package also brings Logpush to self-serve plans and introduces a unified pricing model for observability data ingested and stored across Cloudflare. For developers and operators, this is a substantial workflow announcement, not another dashboard with a fresh coat of pixels.
Cloudflare Watch analysis
What happened
In its 2 October announcement, Cloudflare described a platform-wide approach to investigating application behaviour. A spike in failed requests might involve a Worker, an origin server or the connection between them; the updates aim to make those signals easier to investigate together.
The new Logs home combines Workers Observability and Log Explorer. Available datasets include HTTP events, firewall events, Workers, Containers, R2 and AI Gateway. Users can switch datasets within Logs, query with SQL or built-in filters, and inspect individual requests by Ray ID.
There is an important distinction: switching between datasets is available, but querying across multiple datasets in a single query is described as coming soon. One front door does not yet mean every room is connected.
Our top picks
- One Logs home across products
Switch between application, storage and security datasets without leaving the investigation interface. - Tracing from edge to origin
Cloudflare says end-to-end tracing connects its edge with the origin, widening the view beyond an individual service. - A unified SQL query API
One API for querying Cloudflare data offers a more consistent route for developers building their own investigative workflows. - Logpush on self-serve plans
Exporting data becomes available to self-serve customers, giving more teams a route into their existing observability tools. - Custom alerts on observability data
Teams can define alerts around their own data rather than relying solely on manual dashboard checks. - Domain analytics with 30-day retention
Domain analytics come together in one place, with a month of retained data for examining patterns over time. - Custom dashboards
Teams can build dashboards from their observability data, arranging the signals around the applications they actually operate. - Unified ingestion and storage pricing
Cloudflare is introducing one pricing model across observability data ingestion and storage, alongside the shared product experience.
Why it matters
Debugging gets slower when the first task is working out which product owns the evidence. The shared Logs interface gives teams a concrete starting point: group a latency increase by hostname or data centre, narrow it to affected paths, then inspect individual requests.
Including AI Gateway alongside Workers and other datasets also makes this useful for teams operating AI-backed applications. Export access matters just as much: a consolidated Cloudflare interface need not become the only place a team keeps its operational evidence.
Our read
This is a worthwhile consolidation. The strongest part is not the number eight; it is the combination of a shared investigation interface, broader tracing and a route to export data on self-serve plans.
Start with a real incident, not a guided tour. Try following a slow request from the affected hostname to the relevant dataset and request identifier. Then check whether the resulting evidence fits your existing monitoring workflow.
Keep the cross-dataset query limitation in view. Switching datasets can reduce friction, but it is not the same as joining related events automatically. That forthcoming capability is a meaningful next test, not a footnote.
What to watch
- When single queries across multiple datasets become available.
- Which additional products and datasets join the shared platform.
- Whether edge-to-origin tracing provides useful continuity on real applications.
- How the unified pricing model affects representative ingestion, storage and export workloads.
Discussion spark: Should teams make Cloudflare’s unified platform their main investigation workspace, or keep an independent observability tool central even as the native experience improves?
Sources and evidence
- Source update (2 October 2026, 18:00 UTC)
not affiliated with or endorsed by Cloudflare