> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloudflare

> Create a Cloudflare Logpush job with an HTTP destination pointed at your Sazabi intake URL to stream edge network logs to Sazabi.

[All Cloudflare integration capabilities](https://docs.sazabi.com/catalogs/integrations/cloudflare)

## About

You can also connect your Cloudflare account to Sazabi and have Sazabi create and manage Logpush jobs automatically. See [Cloudflare (connect your account)](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/cloudflare.md) for that path.

This page covers the manual endpoint configuration: create a Logpush job yourself and point it at your Sazabi intake URL. Use this approach when you want to manage the Logpush job directly or when the connect-your-account path is not suitable for your setup.

Cloudflare Workers telemetry (console output and OTLP traces) comes from a separate source. See [Cloudflare Workers](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/cloudflare-workers.md).

## Prerequisites

* A Cloudflare account on any plan. Logpush is available on every plan since September 30, 2026; Free, Pro, and Business accounts pay Cloudflare per GB beyond the included monthly usage ([Logpush pricing](https://developers.cloudflare.com/logs/logpush/pricing/)). The `workers_trace_events` dataset needs the Workers Paid plan.
* An API token with: Account Settings Read, Zone Read, and Zone Logs Edit permissions (when creating a zone-scoped job), or Account Logs Edit (when creating an account-scoped job; Zero Trust datasets also need Zero Trust PII Read).
* Your Sazabi intake URL, shown above — open the log source and copy the **Intake URL** from its setup screen (the public key is embedded in the URL).

## Set up in the dashboard

**Step 1**

### Open Logpush in the Cloudflare dashboard

In the Cloudflare dashboard, navigate to your zone or account, then go to **Analytics & Logs > Logpush**. Click **Create a Logpush job**.

**Step 2**

### Select a dataset and destination

Choose the dataset you want to stream (for example, HTTP requests, Firewall events, or DNS logs). When prompted for a destination, select **HTTP** and paste your Sazabi intake URL shown above.

**Step 3**

### Set the timestamp format to RFC3339

In the Logpush job output options, set the timestamp format to **RFC3339**. Sazabi requires RFC3339 timestamps to parse event times correctly.

> [!WARNING]
>
> Set the timestamp format to RFC3339 in the Logpush job output options. Other
> timestamp formats may cause events to be stored without a parseable timestamp.

**Step 4**

### Save and enable the job

Save the Logpush job. Once saved, the job starts streaming.

## Set up with the CLI

You can also register the Cloudflare log source with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [CLI reference](https://docs.sazabi.com/reference/cli/log-sources.md)).

Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):

```bash theme={"system"}
sazabi log-sources create cloudflare --mode manual
```

The command prints the intake URL for the new source — copy the whole URL and point your sender at it using the configuration shown above. Run `sazabi log-sources get <log-source-id>` at any time to reprint the endpoint, or `sazabi log-sources list` to see every log source in the project.

## Verify

Generate traffic on the zone or account you configured (for example, make an HTTP request to your Cloudflare-proxied domain). Open the [Intake page](https://docs.sazabi.com/guides/instrument/intake.md) in the Sazabi dashboard and confirm records from the **Cloudflare** source appear within a minute or two.

## Troubleshooting

**No records arrive** — Confirm the intake URL was pasted correctly into the Logpush HTTP destination and that the zone or account is generating traffic on the selected dataset.

**Records appear but timestamps are wrong** — Confirm the Logpush job output options use RFC3339 timestamp format. Other formats are not parsed correctly.

**Missing datasets** — Most Logpush datasets need the Cloudflare product that produces them, and `workers_trace_events` needs the Workers Paid plan. If a dataset does not appear in the Logpush UI, check the Cloudflare documentation for that dataset's requirements.

## Further reading

> [card] [Intake](https://docs.sazabi.com/guides/instrument/intake.md)
>
> See per-source ingestion volume and health.

> [card] [Cloudflare (connect your account)](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/cloudflare.md)
>
> Let Sazabi create and manage Logpush jobs automatically.

> [card] [Log sources](https://docs.sazabi.com/catalogs/log-sources.md)
>
> Browse the full log source catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.