Cloudflare
Stream Cloudflare Workers logs and traces to Sazabi for edge network observability.
Stream your Cloudflare Workers logs and traces directly to Sazabi for edge network observability. Monitor Workers executions, binding calls, and fetch requests with real-time AI-powered analysis.
About this data source
Cloudflare Workers Observability supports exporting logs and traces to external OTLP endpoints. By configuring a destination pointing to Sazabi, you can:
- Monitor Workers execution performance and errors
- Trace requests through your edge infrastructure
- Analyze binding calls to KV, D1, R2, and other services
- Detect performance issues and anomalies with AI assistance
- Keep Cloudflare as your edge platform while gaining unified observability
Prerequisites
Before you begin, make sure you have:
- A Cloudflare account with Workers deployed
- Workers Observability enabled for your account
- A Sazabi public API key (project-scoped)
Get your API key
Create a public key
Click Create API key and select Public as the key type. Public keys are safe to use in external configurations and are scoped to a single project.
Copy the key and store it securely. You will not be able to see it again.
Setup
Open Cloudflare Workers Observability
Navigate to your Cloudflare dashboard and go to Workers & Pages > Observability.
Add a destination
Click Add destination to configure a new telemetry export destination.
Configure OTLP endpoints
Enter the Sazabi intake endpoints for logs and traces:
- Logs endpoint:
https://otlp.<region>.intake.sazabi.com/v1/logs - Traces endpoint:
https://otlp.<region>.intake.sazabi.com/v1/traces
Replace <region> with your Sazabi project region (e.g., us-east-1).
Add authorization header
Configure the authorization header for both endpoints:
- Header Name:
Authorization - Header Value:
Bearer <your-api-key>
Replace <your-api-key> with your Sazabi public API key.
Save and enable
Save your destination configuration. Cloudflare will begin forwarding telemetry from your Workers to Sazabi.
How it works
Cloudflare automatically instruments your Workers with no code changes required. When configured:
- Your Workers execute on Cloudflare's edge network
- Cloudflare captures execution logs and traces automatically
- Telemetry is batched and sent to Sazabi's OTLP endpoints
- Sazabi processes and stores the data for analysis
- Chat can search, filter, and analyze your Workers telemetry
What gets captured
Cloudflare Workers Observability captures:
- Request logs: Incoming HTTP requests and responses
- Console output:
console.log,console.error, and other console methods - Binding calls: Interactions with KV, D1, R2, Queues, and other bindings
- Fetch traces: Outbound HTTP requests made by your Workers
- Execution metadata: Cold starts, CPU time, and wall time
Verifying telemetry is flowing
Once configured, verify that telemetry is flowing to Sazabi:
-
Trigger a Worker: Make a request to one of your Workers endpoints.
-
Ask the assistant: Open a thread in Sazabi and ask "Show me recent Cloudflare Workers logs" or "What errors occurred in my Workers today?"
Troubleshooting
Logs not appearing in Sazabi
- Verify the destination is enabled in Cloudflare Workers Observability
- Check that both endpoint URLs include the correct region
- Ensure the Authorization header is configured correctly
- Make a request to your Workers to generate telemetry
401 Unauthorized errors
- Your API key may be invalid or expired
- Verify the Authorization header format is
Bearer <key> - Create a new public API key in Settings > API Keys
Workers Observability not available
Workers Observability may require specific Cloudflare plan features. Check your account settings or contact Cloudflare support.