Skip to content

Cloudflare Opens Its Telemetry to AI Agents, Resets Pricing

Short answer

Cloudflare unified logs, traces, analytics, alerts and dashboards into one observability platform, adding a SQL API queryable by AI agents via CLI or an Observability MCP server, open-beta tracing, and usage-based pricing starting December 1, 2026. Agents can now query Cloudflare's own telemetry and receive webhook alerts to start investigating incidents directly.

What this means for operators

For a 10-200 person company running Workers, R2, or AI Gateway on Cloudflare, this removes a chunk of integration work needed to make an AI ops or support agent actually useful during an incident: instead of building separate connectors for logs, traces, and analytics, an agent can hit one SQL API or the new Observability MCP server, and alerts can route straight to that agent via webhook before a human even opens a dashboard. Logpush moving off Enterprise-only plans also means smaller teams can now export raw logs to their own tools for agent training or audit trails without an enterprise contract, though the new per-GB pricing landing in December 2026 is worth checking against current log volume.

Cloudflare announced eight updates consolidating its observability tooling into a single platform: a combined Logs home, open-beta request tracing, a unified SQL API, new alerts, 30 days of domain analytics on every plan, custom dashboards, and Logpush now available on all self-serve plans.

The update most relevant to automated operations is the new unified SQL API, now in beta, which lets both people and agents query Workers logs, Container security events, HTTP request logs, and analytics data through one SQL dialect and authentication model. Agents can reach it through Cloudflare's new CLI (cf) or through an Observability MCP server built for this purpose. The SQL interface is also being added as a native binding inside Workers, so a Worker can query its own Analytics Engine data to meter usage, power billing, or automate incident investigation without a separate API client.

Alerts (formerly called Notifications) are getting the same treatment: custom conditions can now be defined directly against any dataset in the SQL API, with thresholds, anomaly detection, or SLO-based triggers. Webhooks, now available on every plan, can route an alert to "custom services or even your agent to begin investigating immediately," per Cloudflare.

Tracing enters open beta with request-level visibility into security rules, routing, Workers, and origin handling, supporting OpenTelemetry export and W3C trace context propagation so trace data can flow between Cloudflare and a company's own origin systems.

Pricing is also changing. Starting December 1, 2026, all ingested and stored logs and traces move to one usage-based model: Free plans get 0.5 GB of ingestion per day with 7-day retention; Paid and Enterprise plans include 50 GB of ingestion and 10 GB-month of storage per billing cycle, with additional usage billed at $0.25 per GB ingested and $0.10 per GB-month stored. Logpush, previously Enterprise-only, is now on all self-serve plans with 25 GB of free exports to Cloudflare or external destinations monthly, billed at $0.03 or $0.10 per additional GB respectively; the accompanying Transformers tool for reshaping log output before delivery is now generally available, with 1 GB free and $0.04 per additional GB.

Cloudflare says longer data retention (up to one year), expanded OpenTelemetry support in Workers, and easier metrics export are planned next.

Source: Cloudflare Blog · In the Atlas: Cloudflare OS →

Next step

Visibility Analyzer

This is what the Visibility Analyzer measures on a real site: which answers cite you, which pages an engine cannot retrieve, and what to fix first. Free to run.

Run a free visibility audit

Free to run. No card.

Fee
Free
Length
One run, minutes

Free tier: two analyses a day, no card required.