SYSTEM Cited by 2 sources

Buftee

Buftee is Cloudflare's internal log-based buffering system — the durable broker that sits between the pipeline's centralized receivers and its downstream consumers. Receivers push ingested, sampled, aggregated events onto Buftee; consumers (ClickHouse inserters, Logpush delivery) fetch from it at their own pace. It is the shared buffering substrate under both Cloudflare's internal analytics pipeline and the external Logpush export path. (Sources: sources/2026-10-13-cloudflare-rewinding-the-exponential, sources/2026-10-12-cloudflare-filter-reshape-redact-logs-transformers)

Role in the analytics pipeline

In the Data team's edge→center pipeline, Buftee is the hand-off point between ingestion and consumption:

Logfwdr (edge) → centralized receivers → Buftee → consumers/inserters → ClickHouse

Two properties make Buftee load-bearing for the 2026 cross-region redesign (Source: sources/2026-10-13-cloudflare-rewinding-the-exponential):

• It is where late replication happens. Instead of Logfwdr double-writing two copies of every event over the WAN, Logfwdr sends each event once to a shared receiver pool; the data lands in Buftee, and remote inserters stream the cross-data-center copy downstream from there. Replication is pushed "as late as possible in the pipeline" — downstream of sampling and of the uniform-batch repartitioning that improves compression. See late replication.
• Its retention buffer absorbs inter-DC link failures. If the inter-data-center connection blips, "each cluster continues ingesting its local share without backpressure; remote inserters catch up from Buftee's retention buffer once the backbone recovers." The buffer is the slack that lets regions operate independently during a partition — a backpressure-decoupling buffer between write side and cross-region read side.

Role in the Logpush export path

Buftee is also the upstream broker for Cloudflare's Logpush export service. Bufstream — Cloudflare's Go Logpush delivery service (>110M Logpush records/s across hundreds of Kubernetes pods) — has each pod claim a time slice of a job's data from Buftee, parse the Cap'n Proto records Buftee delivers, run the Transformer SQL, and upload. (Source: sources/2026-10-12-cloudflare-filter-reshape-redact-logs-transformers) In that path Buftee is described as "Cloudflare's in-house log-based broker."

Seen in

• sources/2026-10-13-cloudflare-rewinding-the-exponential — Buftee as the pipeline buffering layer that late replication inserts after (remote inserters stream the second ClickHouse copy from Buftee, not from Logfwdr at source) and whose retention buffer lets each cluster keep ingesting without backpressure during an inter-DC link blip. The property that makes the shared-ingest-pool + late-replication redesign resilient.
• sources/2026-10-12-cloudflare-filter-reshape-redact-logs-transformers — Buftee as the in-house log-based broker upstream of Bufstream in the Logpush export path; Bufstream pods each claim a time slice of a job's data from Buftee and parse its Cap'n Proto records.

Related

• systems/logfwdr — the edge forwarder whose receivers push onto Buftee; the double-write → shared-pool redesign moved replication to after Buftee.
• systems/bufstream — the Logpush delivery service that claims time slices from Buftee and runs Transformer SQL on them.
• systems/clickhouse — the analytics destination the inserters write to after reading Buftee.
• systems/cloudflare-logpush — the export product Buftee buffers for.
• patterns/async-replication-for-cross-region — Buftee is the point after which the cross-region copy is made (late replication).
• concepts/backpressure — Buftee's retention buffer is the slack that decouples ingest from cross-region catch-up.
• companies/cloudflare — operator.