8 major updates to Cloudflare Observability
- ID
- 31131
- Status
- summarized
- Published
- 02 Oct 2026, 9:00 PM
- Fetched
- 02 Oct 2026, 10:45 PM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/one-observability-platform/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 5.5
- Created
- 02 Oct 2026, 10:46 PM
- Tags
- Audience
- developersvibe_codersstartup_founders
What happened
Cloudflare announced eight updates to its Observability stack on October 2, 2026, consolidating logs, traces, analytics, alerts, dashboards, and exports into one platform. Concretely: a combined Logs home merging Workers Observability with Log Explorer across datasets including HTTP events, firewall events, Workers, Containers, R2 and AI Gateway; Cloudflare Traces in open beta giving request-level views from edge to origin; a unified SQL API for querying Cloudflare data; custom alerts and dashboards; 30-day analytics retention; and Logpush now available on self-serve plans. Cloudflare also says it is moving to one pricing model for observability data ingested and stored across the platform, with cross-dataset querying listed as coming soon.
Why it matters
If you already run Workers, R2, or AI Gateway, this is a concrete change in where you debug and what you pay for: Logpush on self-serve plans removes the plan upgrade that previously gated exporting logs, and 30-day analytics retention plus a single SQL API means you can drop some separate log-shipping or query tooling. The pricing consolidation is the item to actually check against your invoice — 'one pricing model for ingested and stored data' changes the cost shape, so re-run your current ingest volume against the new model before committing to it, and note that cross-dataset queries are still 'coming soon', so don't design a workflow that depends on them yet.
Discussion angle
Is a single-vendor observability platform with one pricing model a simplification or lock-in? Compare the effort of keeping logs in Cloudflare's SQL API versus piping Logpush into an existing stack — and ask who has actually measured their ingest volume against the new pricing.