Connect client traces to your logs

Summary

supabase-js now supports W3C Trace Context propagation so a client trace can share its trace_id with Supabase API Gateway and Edge Function logs. Previously, browser and server records had no shared identifier, making cross-boundary debugging depend on manually aligning timestamps. When tracePropagation is enabled, the SDK attaches traceparent, tracestate, and baggage to requests for Supabase domains; Supabase preserves the trace_id in generated logs, and W3C-compliant tracers such as OpenTelemetry, Sentry, Datadog, Honeycomb, or Grafana can continue the trace server-side. The setup requires a separately configured tracer, the tracing entry-point import, an active span, and a registered TracerProvider; propagation is sampling-aware by default, adds no OpenTelemetry code to the main bundle, and is available in supabase-js 2.112.0 or later, with CDN/UMD builds excluded.

Takeaways

1. 1

   tracePropagation sends traceparent, tracestate, and baggage only to Supabase project hosts, Supabase domains, and listed local development hosts, not third-party hosts.

2. 2

   The integration requires an active span and a registered TracerProvider; without them, the SDK silently performs no propagation. Sampling decisions are respected unless respectSamplingDecision is set to false.

3. 3

   The tracing integration is excluded from the main supabase-js bundle and is unavailable in CDN/UMD builds. Bundled applications using versions 2.106.0 through 2.111.x should upgrade to 2.112.0 or later.