You can now get a single unified trace across Worker-to-Worker subrequests, with trace context propagating automatically. Previously, automatic tracing produced disconnected traces when a Worker called another Worker through a service binding or Durable Object.
This means you can:
- Follow a request through your entire Worker architecture in one trace view
- See service binding and Durable Object calls as nested child spans instead of separate traces
- Debug cross-Worker request flows in the Cloudflare dashboard or in an external observability platform via OpenTelemetry
Tracing must be enabled in your Wrangler configuration for traces to be recorded. Checkout Workers tracing to get started.
Up next, we are working on external trace context propagation using W3C Trace Context standards, which will allow traces from your Workers to link with traces from services outside of Cloudflare.
Source: Cloudflare
Latest Posts
- AWS Lambda recursive loop detection is now available in all commercial AWS Regions
- Amazon Timestream for InfluxDB is now available in 8 additional AWS Regions
- AWS Agent Registry for centralized agent discovery and governance is now generally available
- AWS announces AWS Interconnect – multicloud connectivity with Microsoft Azure in preview
