Cloudflare folds eight observability tools into one platform

Cloudflare has pulled eight updates to its logging, tracing and analytics products into a single observability platform, and redrawn the pricing that sits underneath them. The company says the aim is to treat observability as a platform-wide capability rather than a set of products a customer has to stitch together by hand.

One home for logs, traces and analytics

The new Logs home combines Workers Observability, which is used to debug Workers applications and their connected resources, with Log Explorer, which searches across security logs. Datasets include HTTP events, firewall events, Workers, Containers, R2 and AI Gateway, and the same investigative tools apply to each, so an investigator can start from a rise in request latency and group it by hostname or other fields without switching products.

Tracing now runs end to end from Cloudflare's edge to the origin, so a spike in 5xx responses can be followed through a Worker, an origin server or the network path between them. A single SQL API queries Cloudflare data across the platform, replacing the previous requirement to know which product owned each signal and how to query it.

One price, more alerts, longer retention

Cloudflare has simplified billing to one model for observability data ingested and stored across its network. Customers can now set custom alerts on their observability data, find all analytics for a domain in one place with 30 days of retention, and build custom dashboards from the same data. Logpush data export, previously reserved for enterprise contracts, is now available on self-serve plans.

The company says more of its products, datasets and workflows will join the shared platform over the coming months, with more consistent pricing and product experiences to follow.

Our opinion

The pitch here is subtraction. Cloudflare is betting that the hard part of observability is no longer storing signal but remembering which dashboard owns which symptom, and the eight updates are really one promise: fewer places to look. Moving Logpush onto self-serve plans is the quietly significant line, because export is what stops a platform being a trap and lets a team keep its own history. The test is whether the unified pricing survives contact with a genuinely noisy service, where ingestion volumes climb faster than anyone expects. Until then this is a tidier console, and a fair one, rather than a solved problem.