Logpush

import { LinkButton } from "~/components";

Logpush delivers logs in batches as quickly as possible, with no minimum batch size, potentially delivering files more than once per minute. This capability enables Cloudflare to provide information almost in real time, in smaller file sizes.

The push frequency is automatic and cannot be adjusted—Cloudflare pushes logs in batches as soon as possible. However, users can configure the batch size using the API for improved control in case the log destination has specific requirements.

:::caution[Important limitation] Logpush only pushes logs once as they become available and cannot backfill historical data. If your job is disabled or fails, logs generated during that period are permanently lost. This is why configuring health notifications is essential for early detection of issues. :::

Logpush does not offer storage or search functionality for logs; its primary aim is to send logs as quickly as they arrive.

Cloudflare Logpush supports pushing logs to storage services, SIEMs, and log management providers via the Cloudflare dashboard or API.

Estimating log volume

Before setting up a Logpush job, you can estimate the total volume of data that will be pushed to your destination. The volume depends on your traffic, the dataset, and the fields you select.

Logpush usage is measured in uncompressed bytes delivered, so estimate with uncompressed record sizes. For rates and included usage, refer to Pricing.

Quick sizing for HTTP Requests

An HTTP Requests record is about 1.5–3 kB uncompressed, depending on the fields selected. Each request produces one record, including Worker subrequests.

• 100k requests/day → ~150–300 MB/day
• 1M requests/day → ~1.5–3 GB/day, or ~45–90 GB/month
• 10M requests/day → ~15–30 GB/day
• 100M requests/day → ~150–300 GB/day

Files arrive at your destination gzip-compressed, so they use roughly a tenth of the storage that the uncompressed volume suggests.

Extra fields and custom fields increase record size. Other datasets (Firewall, Workers, Load Balancing) add volume separately. For average record sizes by dataset, refer to Log Explorer pricing.

For precise estimates, you can sample your logs via Logpull using a 1-hour sample.

Limits

Logpush job limits depend on your plan, dataset, and job scope:

Existing Enterprise customers may retain a default limit of four jobs per dataset. Cloudflare can adjust this limit manually. Dataset-specific entitlements may also set different limits. Instant Logs supports two jobs per zone.

If you reach a limit, the API returns creating a new job is not allowed: exceeded max jobs allowed.

Availability

Dataset availability depends on the Cloudflare products on your account. Workers Trace Events Logpush requires the Workers Paid plan and retains separate request-based pricing.

For usage rates and included monthly usage, refer to Pricing.