Cloudflare CLI cf reaches a 1.0 release candidate
The unified Cloudflare CLI stabilises its config format, build output and core commands, but existing beta projects need updating before they can move to it.
Tagged
The unified Cloudflare CLI stabilises its config format, build output and core commands, but existing beta projects need updating before they can move to it.
Uncaught exceptions and unhandled rejections, grouped into issues with stack traces and occurrence counts, in the analytics tool you may already be self-hosting.
Request tracing is now generally available on every Vercel plan, with Pro retention up from one day to fourteen and a new searchable Traces page.
Projects created from 5 November get request tracing out of the box, with no setup, but it bills by the span and quietly adds @vercel/otel to every build.
A natural-language query tool for agent traces that finds behavioural patterns, such as silent failures or PII leaks, without a pre-built evaluator.
Messages API requests and Managed Agents sessions can now stream standard OTel spans into Datadog, Grafana, Honeycomb and ten other observability tools.
The Cloudflare API MCP server now streams Workers Issues as signed webhook events, so an agent can react to a production failure without polling for it.
Real User Monitoring now reports the phases behind each Core Web Vital, so you can see whether a slow LCP is a server, network or render problem.
A new dashboard view shows which Cloudflare location served the most read and write traffic for an R2 bucket, instead of just a single global total.
A changelog update means Cloudflare now consistently records a cancelled HTTP/3 request as a 499, instead of sometimes letting it carry on to origin.
A unified Logs home, SQL API and traces beta ship alongside news that observability pricing moves to volume-based billing on every plan from 1 December.
startSpan, getActiveSpan, recordException and setAttributes let you instrument Workers code without threading span objects through every function call.