Distributed Tracing Across Cloudflare RPC Service Bindings

[invalidred]

Feature Request: Distributed Tracing Across Cloudflare RPC Service Bindings

Context

We operate a backend monorepo built on Cloudflare Workers, where an API gateway service communicates with multiple backend RPC services using Cloudflare RPC service bindings. These backend services may also call one another via service bindings and interact with external systems such as databases and caches.

Problem

When viewing traces in Cloudflare observability today, tracing data is isolated to individual services. Trace context does not appear to propagate automatically across RPC service bindings, which results in:

• Separate, disconnected traces per service
• No unified request-level view of how a single client request flows through multiple RPC services
• Inability to accurately understand latency breakdowns, fan-out behavior, or failure propagation across services

This makes it difficult to debug production issues or reason about end-to-end request performance in a microservice architecture built on service bindings.

Desired Behavior / Feature Request

We would like first-class, end-to-end distributed tracing support across Cloudflare RPC service bindings, such that:

• A single client request produces one stitched trace
• Trace context is automatically propagated across:
  • RPC service bindings
  • Downstream service-to-service calls
  • External systems (e.g., databases, caches)
• The trace clearly shows parent/child relationships between services and RPC calls

Expected Trace Structure

Client
 └─ API Gateway
     └─ Backend Service A
         ├─ RPC → Service B
         │    └─ DB query
         └─ RPC → Service C
              └─ Cache lookup

Why This Matters

Distributed tracing across RPC boundaries is critical for:

• Debugging latency and errors in production
• Understanding request fan-out and bottlenecks
• Operating Cloudflare Workers as a true microservice platform at scale

Without trace stitching across service bindings, observability is incomplete and does not reflect real request behavior.

Ask

Is Cloudflare planning to support automatic trace context propagation and trace stitching across RPC service bindings?
If not, is there a recommended pattern or roadmap item to enable this behavior?