Connect client traces to your logs
The supabase-js library now automatically propagates W3C Trace Context headers in outgoing requests. This enables the correlation of client-side traces with server-side Supabase logs using a shared trace_id.
Verified State Diff
Impact & Verification Analysis
Full-stack developers and DevOps engineers using Supabase for distributed applications.
It significantly reduces mean time to resolution (MTTR) for production issues by enabling end-to-end observability and request debugging across the entire stack.
Full Fact Overview
By implementing W3C Trace Context propagation, Supabase has bridged the observability gap between frontend client applications and backend infrastructure. Previously, logs generated by Supabase services were isolated from the client-side execution context, making distributed tracing across the network boundary impossible. With this update, the traceparent header is injected into requests, allowing observability platforms to stitch together a unified request lifecycle from the browser or mobile client through to the Supabase database and API layers.