3.5 KiB
3.5 KiB
Observability Configuration
Fetch the relevant guide before configuring the selected Worker and deployment environment.
| Task | Maintained documentation |
|---|---|
| Enable persisted logs, structured JSON logging, and sampling | Workers Logs |
| Enable traces and set their sampling independently of logs | Workers Traces |
| Configure a named deployment environment | Wrangler environments and the environment example in Workers Logs |
| Bind an Analytics Engine dataset and write its first data point | Analytics Engine get started |
| Connect a producer to a Tail Worker | Configure Tail Workers |
| Create a Logpush job, configure access, and enable Worker log delivery | Workers Logpush |
| Configure OTLP destinations, authentication, and local persistence | Exporting OpenTelemetry data |
Setup decisions
- Confirm which account, Worker, and environment will emit telemetry, then deploy that configuration and generate representative traffic.
- Decide log and trace sampling separately. Increasing sampling during an investigation changes volume and cost; restore the intended operational settings afterwards.
- For Tail Workers, configure the consumer relationship on the producer Worker; use the guide for deployment order and the handler contract.
- Choose whether to persist data in Cloudflare as well as exporting it. Verify destination names, supported signal types, and credentials using the export guide.
- Use stable structured fields and redact secrets and unnecessary personal data before emission. Configure development and production collection intentionally.
See gotchas.md when configured telemetry is missing.