cloudflare-workers-otel-utels

You add OTLP telemetry to Cloudflare Workers by wrapping your fetch handler with the withTelemetry wrapper, which automatically emits traces, metrics, and logs to your configured OTLP endpoints without changing core business logic.

Yes, you can track D1 query performance non-intrusively. The instrumentation wraps D1 query telemetry and related bindings to surface slow queries and performance data without requiring modifications to your application code.

You need to set OTEL_EXPORTER_OTLP_ENDPOINT or specific traces, metrics, and logs endpoints. If using utels error tracking, you must also configure UTELS_ENDPOINT, UTELS_PROJECT_ID, and UTELS_INGEST_TOKEN.

Automated error reporting is set up by wrapping your worker's fetch handler with withUtelsErrorTracking, which sends exception events to a utels project using your configured UTELS_ENDPOINT, UTELS_PROJECT_ID, and UTELS_INGEST_TOKEN.

The best way to get end-to-end request visibility is using lightweight wrappers like withTelemetry and withUtelsErrorTracking, which integrate with OTLP backends to collect traces, metrics, logs, and exception events from request to response.

No, wrapping fetch handlers for observability does not require changing your business logic. The wrappers provide non-intrusive instrumentation around the handler to emit telemetry and track errors without altering the core code.