Expanding the Cloudflare Workers Observability Ecosystem

Workers Observability Gets a Full-Stack Boost

Running code at Cloudflare's edge—"region Earth," as the company puts it—means there are no availability zones to provision or scaling policies to tune. But that same distributed model makes production visibility harder. Once a Worker is live, you need to know what it's doing, why it's failing, and what your users are experiencing. Cloudflare is extending its observability ecosystem with six new integrations aimed at closing that gap. The company is bringing on Sentry and New Relic as application-level monitoring partners and expanding existing relationships with Datadog, Splunk, Sumo Logic, and Honeycomb to cover Worker-specific telemetry.

From Console.log to Application Monitoring

The quickest way to see what a Worker is doing is still a console.log statement. The wrangler dev and wrangler tail CLI commands surface that output during development and testing. For production, however, teams need more: version awareness, context around errors, and the ability to correlate client-side events with server-side execution.

Sentry, now an official observability partner, handles error tracking and performance monitoring for Worker code. Cloudflare's own Robert Cepa maintains toucan-js, an open-source Sentry client built specifically for Workers. After an npm install toucan-js and minimal setup, you can replace basic logging with Sentry's data stream. Captured events show up as a user journey with filters, timestamps, and versioning, which helps developers trace what happened before an error occurred.

New Relic takes a different route. There is no dedicated npm package yet, but you can pipe Worker logs to New Relic's HTTPS log endpoint. The key is using event.waitUntil() so log delivery doesn't block the request and drag down performance. Once the data lands in New Relic One, it's available for analysis alongside the rest of your telemetry.

"Monitoring your Cloudflare Workers serverless environment with New Relic lets you deliver serverless apps with confidence by rapidly identifying when something goes wrong and quickly pinpointing the problem—without wading through millions of invocation logs."

Edge and Origin Logs in One Place

Application-level monitoring tends to focus on individual services. Observability platforms, by contrast, provide a whole-infrastructure view with alerting on anomalies across every component. Cloudflare's existing analytics partnerships with Datadog, Splunk, and Sumo Logic now support Worker-specific fields such as WorkerCPUTime, WorkerStatus, WorkerSubrequest, and WorkerSubrequestCount in edge HTTP logs.

All three platforms expose HTTP ingestion APIs—Datadog's HTTP API, Splunk's REST API, and Sumo Logic's HTTP Logs and Metric Source. With those, you can feed application logs from your Workers into the same ingestion engine that handles origin logs. For security teams, this means Worker activity can be treated as a first-class citizen in a detection-and-response workflow, not a blind spot.

"Maintaining a strong security posture means ensuring every part of your toolchain is being monitored - from the datacenter/VPC, to your edge network, all the way to your end users."

Event-Based Debugging at Scale

Honeycomb's approach differs from traditional metrics-and-dashboards tooling. Instead of aggregating into charts that obscure individual users, it uses an event-based model with a query engine that can slice across billions of rows. The BubbleUp feature automatically compares "good" sets of events against "bad" ones to surface what distinguishes them. That helps teams skip the usual drill-down guessing game and find the root cause of an incident faster.

The beta @cloudflare/workers-honeycomb-logger npm module has first-class awareness of sub-requests, a core pattern in many Worker applications, and surfaces that structure directly in the platform.

"Understanding how that code performs and behaves when it is in the hands of users also determines success."

The Operational Lifecycle

Workers are easy to deploy; the hard part is operating them once they're handling traffic. The new and expanded integrations complement the built-in CLI tools, shifting the experience from development to production. The common thread across Sentry, New Relic, Datadog, Splunk, Sumo Logic, and Honeycomb is that each accepts HTTP-based log ingestion, giving developers a path from streaming logs to structured telemetry without swapping out their team's existing infrastructure.