Cloudflare Workers

Add OTLP log and trace destinations in Cloudflare Workers Observability settings and opt each Worker in via wrangler config to stream telemetry to Sazabi.

About

Stream console output and OTLP traces from your Cloudflare Workers directly to Sazabi using Cloudflare's native Workers Observability feature. You configure OTLP destinations at the account level and then opt each Worker in through its wrangler.jsonc or wrangler.toml configuration.

Cloudflare Logpush datasets (HTTP requests, Firewall events, DNS logs) come from a separate source. See Cloudflare for that setup.

Prerequisites

Cloudflare Workers Observability access on your Cloudflare account
Your Sazabi OTLP intake URLs for logs and traces (shown above)
Workers deployed via Wrangler

Set up in the dashboard

Open Workers Observability in the Cloudflare dashboard

In the Cloudflare dashboard, navigate to Workers & Pages > Observability > Telemetry > Add Destination.

Add a logs destination

Create a new destination with the following settings:

Destination type: Logs
Name: sazabi-logs
Endpoint: your Sazabi OTLP logs intake URL (shown above, ending with /v1/logs)

Add a traces destination

Create a second destination with the following settings:

Destination type: Traces
Name: sazabi-traces
Endpoint: your Sazabi OTLP traces intake URL (shown above, ending with /v1/traces)

Opt each Worker in via wrangler config

In each Worker's wrangler.jsonc or wrangler.toml, enable Workers observability and list the log and trace destination names you created (sazabi-logs and sazabi-traces). Refer to Cloudflare's Wrangler configuration reference for the exact keys.

Redeploy each Worker

Run wrangler deploy for each Worker whose configuration you updated. Workers Observability takes effect on the next deployment.

Set up with the CLI

You can also register the Cloudflare Workers log source with the Sazabi CLI (installed and authenticated — see CLI reference).

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

sazabi log-sources create cloudflare_workers --mode connectionless

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

Invoke a Worker that you opted in (for example, make an HTTP request to its route). Open the Intake page in the Sazabi dashboard and confirm logs or traces from the Cloudflare Workers source appear within a minute or two.

Troubleshooting

No telemetry after redeploying — Confirm the Worker's wrangler.jsonc/wrangler.toml enables observability and lists the destination names, and that those names match exactly what you created in the Cloudflare dashboard (case-sensitive).

Logs appear but traces do not — Verify both the logs and traces destinations are created in the Cloudflare dashboard and both destination names appear in the Worker's wrangler config.

Destination not found error — Destinations are account-scoped. Confirm you created the destination in the same Cloudflare account that owns the Workers you are configuring.