Cross‑Worker JavaScript RPC Tracing Now Captures Session Spans

Cloudflare Workers now extend JavaScript RPC tracing to include session spans that travel across Worker boundaries and into Durable Objects. The change means a single trace can show the full lifecycle of a caller‑side session, the individual method calls it makes, and any callbacks that return, all without modifying application code.

What Changed in Tracing

Previously a trace stopped at the point where a Worker made an RPC call. The new implementation records a session span that covers the entire caller‑side session and groups together all calls that reuse that session. Each method invocation appears as an individual call span. The dashboard distinguishes entrypoints with different colors and uses arrows to indicate outgoing and incoming calls, making it clear where time was spent and how stubs and callbacks fit into the request flow.

Why It Matters for Engineers

For AI, cloud, DevOps, and security engineers the added visibility reduces the time needed to diagnose latency or unexpected behavior in distributed Worker workloads. Because the spans are generated automatically, teams do not need to add an observability SDK or instrument code, preserving deployment simplicity while still gaining detailed performance data. The ability to see which calls reuse a session helps identify inefficient patterns, such as unnecessary RPC hops or excessive callback nesting.

Operational and Architectural Implications

Enabling the feature requires a single flag in the Wrangler configuration:

{
  "$schema": "./node_modules/wrangler/config-schema.json",
  "observability": {
    "traces": {
      "enabled": true
    }
  }
}

or in wrangler.toml:

[observability.traces]
enabled = true

Because the tracing is automatic, existing CI/CD pipelines and monitoring stacks can start ingesting the new spans without code changes. Teams should verify that their observability back‑ends can handle the additional span types and that retention policies account for the longer session data.

Security Considerations

The automatic capture includes method names and timing information that may be visible in the Cloudflare dashboard. Practitioners should treat this data as part of their observability surface and ensure that access controls on the dashboard align with their internal security policies. No new data is sent from the Worker code itself, but the expanded visibility could expose internal call patterns that were previously hidden.

Related CloudNinjas coverage: hands-on guides.

What This Means For Practitioners

• Turn on observability.traces.enabled in your Wrangler config to start receiving session spans.
• Update monitoring dashboards to display the new session and call spans for end‑to‑end request tracing.
• Review retention and access policies for trace data, as more detailed call information will be stored.
• Use the session‑level view to spot inefficient RPC reuse or unexpected callback chains in production workloads.