Deeper Visibility Into Workers With Logpush

Building an application is complex. After deployment, developers need a clear view of what their code is doing in production — not just at a high level, but at the level of individual requests, log messages, and exceptions. Cloudflare is expanding the observability toolkit for Workers with Logpush for Worker's Trace Events, a new option for Enterprise customers to stream raw execution logs to their own storage or analysis systems.

From Quick Glances to Raw Logs

Cloudflare already offers several ways to observe Workers:

  • Workers metrics and analytics for aggregated trends
  • Dashboard logs for on-demand inspection
  • wrangler tail for live debugging during development
  • Third-party integrations with Sentry, New Relic, and Datadog

These tools are useful for targeted debugging, spotting patterns, and monitoring through external platforms. They are designed for ease of use, giving developers quick visibility without extra configuration.

As Workers adoption grows among larger enterprises and platform companies, the need for raw, detailed logs becomes more significant. SaaS providers building on Workers, in particular, require access to underlying execution data to support their own customers' debugging efforts.

What the New Dataset Includes

Logpush for Worker's Trace Events brings Workers execution logs into the same system Cloudflare uses for CDN, WAF, Spectrum, and other products. The dataset includes unstructured console.log() messages, exceptions, and request/response metadata.

A sample Trace Event for a fetch request contains the event type, outcome, duration, CPU time, script name, account ID, and the full request details including URL, method, headers, and Cloudflare-specific fields such as cf data, country, and ASN. Subrequests made by the Worker are also captured, along with their logs and exceptions.

Enterprise customers can route these logs to cloud storage destinations like GCS or R2, or into analysis platforms such as Splunk and New Relic. Logpush manages the batching and scales automatically with traffic volume, so there is no need to worry about data volume limits.

Use Cases for Raw Execution Data

With this new dataset, developers can answer more specific operational questions:

  • Identify exactly when a fetch request fails and why
  • Determine which subrequest adds the most latency to an application
  • Search for particular log lines to trace user-facing issues
  • Correlate Workers logs with HTTP request logs for a complete picture of the request lifecycle

SaaS companies gain a practical path to offering their customers visibility into application performance and sharing logs with end developers for troubleshooting, without building their own logging infrastructure.

Part of a Larger Observability Suite

Logpush for Trace Events fits alongside other observability tools Cloudflare has been rolling out. wrangler tail remains the tool for development-time debugging. Workers Analytics Engine, announced for later this week, enables instrumenting business logic and querying aggregates for dashboarding. Logpush addresses the need for precise, archived records of what occurred in production.

Logpush for Worker's Trace Events will be available to Cloudflare Enterprise customers soon. No additional details on pricing or availability timelines have been announced.