You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
supabase-js now propagates W3C Trace Context to Supabase. Turn on tracePropagation and the trace_id from your client flows through Supabase's API Gateway and Edge Function logs, so you can follow one request from the browser into your backend logs. It is available now in supabase-js, Swift, Flutter, and Python, and works with the tracer you already run.
What changed
Until now, a client-side trace and the Supabase logs for the same request didn't share an identifier, so correlating the two meant guessing from timestamps alone.
What's included
W3C Trace Context propagation (traceparent, tracestate, and baggage) on requests to Supabase domains
The same trace_id stamped on API Gateway and Edge Function logs
Works with any W3C-compliant tracer: OpenTelemetry, Sentry, Datadog, Honeycomb, and Grafana
Opt-in in two steps: import '@supabase/supabase-js/tracing' once at your entry point, then tracePropagation: true in createClient
A sampling override (respectSamplingDecision: false) to carry Supabase requests even when your sampler drops most traces
With Log Drains on, every drained log carries the same trace_id, so it joins your traces in the tracing UI you already run
If you are not using a tracer or Log Drains, nothing changes. Trace propagation is opt-in.
Feedback welcome
If you turn this on, we'd like to hear how it fits your setup, and which tracers and drains you're pairing it with. Reply here, we'll read every comment.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
What changed
Until now, a client-side trace and the Supabase logs for the same request didn't share an identifier, so correlating the two meant guessing from timestamps alone.
What's included
Getting started
Blog post: https://supabase.com/blog/connect-client-traces-to-your-logs
Client-side tracing guide: https://supabase.com/docs/guides/monitoring-and-debugging/client-side-tracing
Log Drains guide: https://supabase.com/docs/guides/monitoring-and-debugging/log-drains
SDK: https://github.com/supabase/supabase-js
If you are not using a tracer or Log Drains, nothing changes. Trace propagation is opt-in.
Feedback welcome
If you turn this on, we'd like to hear how it fits your setup, and which tracers and drains you're pairing it with. Reply here, we'll read every comment.
All reactions