Skip to content
Cloudflare Docs

Observability

Cloudflare Workers provides comprehensive observability tools to help you understand how your applications are performing, diagnose issues, and gain insights into request flows. Whether you want to use Cloudflare's native observability platform or export telemetry data to your existing monitoring stack, Workers has you covered.

Logs

Logs are essential for troubleshooting and understanding your application's behavior. Cloudflare offers several ways to access and manage your Worker logs.

Workers Logs Automatically collect, store, filter, and analyze logs in the Cloudflare dashboard.
Real-time logs Access log events in near real-time for immediate feedback during development and deployments.
Tail Workers Apply custom filtering, sampling, and transformation logic to your telemetry data.
Workers Logpush Send Workers Trace Event Logs to supported destinations like R2, S3, or logging providers.

Traces

Tracing gives you end-to-end visibility into the life of a request as it travels through your Workers application and connected services. With automatic instrumentation, Cloudflare captures telemetry data for fetch calls, binding operations (KV, R2, Durable Objects), and handler invocations - no code changes required.

Metrics and analytics

Metrics and analytics let you monitor your Worker's health with built-in metrics including request counts, error rates, CPU time, wall time, and execution duration. View metrics per Worker or aggregated across all Workers on a zone.

Query Builder

The Query Builder helps you write structured queries to investigate and visualize your telemetry data. Build queries with filters, aggregations, and groupings to analyze logs and identify patterns.

Exporting data

Export OpenTelemetry-compliant traces and logs from Workers to your existing observability stack. Workers supports exporting to any destination with an OTLP endpoint, including Honeycomb, Grafana Cloud, Axiom, and Sentry.

Debugging

Errors and exceptions Understand Workers error codes and debug common issues.
Source maps and stack traces Get readable stack traces that map back to your original source code.
DevTools Use Chrome DevTools for breakpoints, CPU profiling, and memory debugging during local development.

Additional resources

MCP server Query Workers observability data using the Model Context Protocol.
Third-party integrations Integrate Workers with third-party observability platforms.