AI Weekly Malaysia

Cloudflare launched Cloudflare Traces in open beta, extending automatic tracing beyond Workers to the whole request path — security rules, transformations, cache decisions, routing, Worker execution, and origin handling appear as spans in one request-level timeline. It ships with a baseline sampling rate plus Trace Rules to override per-matching-traffic, W3C traceparent context propagation, in-dashboard timelines, and OTLP export to any compatible endpoint. Cloudflare says its own teams debug with internal traces that can hit thousands of spans per request across dozens of services, and Workers Tracing (with KV, R2, D1 and Durable Objects instrumentation) was the earlier step in exposing that.

Why: If you already run Cloudflare in front of an origin, you can enable tracing per domain in the dashboard with no code changes, which means cache-hit/miss and rule-evaluation decisions stop being guesswork when you're debugging latency. The Trace Rules override matters for cost and noise: you can keep the baseline sampling low and only capture full traces for the traffic you actually care about, and the OTLP export plus W3C traceparent forwarding means these spans can land in your existing backend instead of forcing you onto Cloudflare-only tooling.

A year after CTO Dane Knecht pledged to make every Cloudflare feature available to everyone, Cloudflare says Logpush and Logpush Transformers have moved off Enterprise-only and onto all plans, including Free, Pro, and Business, via self-service pay-as-you-go. New Logpush datasets added include account-scoped firewall events, WebSocket analytics, and per-zone post-quantum visibility, and Transformers lets you filter, redact, enrich, and reformat logs with SQL before delivery without running a separate extraction pipeline. Cloudflare states the goal of every feature being available to everyone is not yet met.

Why: If you're on a Free, Pro, or Business plan, you may now be able to export Cloudflare logs directly instead of hand-rolling a Workers-based log shipper or buying an Enterprise contract just for Logpush — and SQL-based Transformers may remove the extraction step from your log pipeline. The post does not state Logpush per-GB pricing or destination limits, so compare the pay-as-you-go rate against your current logging vendor before switching, and check which datasets are actually exposed on your plan tier.

Cloudflare launched Issues, built-in error monitoring for Cloudflare Workers, now in open beta, announced September 30, 2026. Enabling it takes one line of configuration with no SDK or app wrapper: it groups repeated uncaught exceptions, failed invocations, HTTP 5xx responses, console.log/console.error output, and stack-trace logs into a single issue showing first occurrence, frequency count, and trend, and also flags runaway alarm conditions and high-volume logging inside loops. Each issue can forward the error, stack trace, logs, traces, and Worker version to a configured coding agent, which can triage, query more data, or open a pull request — Cloudflare supplies a CF CLI prompt that diagnoses, fixes locally, runs checks, shows the diff, and asks before deploying.

Why: If your team already runs Workers, you can turn this on without adding instrumentation and stop hand-copying logs into your agent — the grouping is the real value, since the example given is one bug producing many different request IDs. If you are not on Workers, nothing here changes your stack. The demo prompt ends with 'Ask before deploying the fix', so if you wire an agent to this, decide the deploy gate yourself rather than assuming the agent will pause.

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: 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.

Cloudflare added a 'model overkill' view to User Insights, the AI usage analytics feature it launched a month earlier inside AI Gateway. It flags conversations where the selected model appears more capable than the task requires — for example, simple formatting or summarization requests sent to a high-capability reasoning model — and shows which users, agents, or applications are driving that pattern alongside task, model, cost, and conversation data. The capability is free for AI Gateway users; the post names no pricing, token volumes, or benchmark numbers.

Why: If your team routes AI traffic through Cloudflare AI Gateway, you can now see whether a model is expensive because the task is hard or just because it's the default — the post calls out 'model is the default' and 'agent configured to use the same model for every step' as two likely causes. If you don't use AI Gateway, this is a Cloudflare-only feature announcement with no measurements, so there is nothing to act on yet. The practical decision is whether visibility into per-user/per-agent model choice is worth routing your AI calls through a single gateway vendor.