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.
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.
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.
Ana introduces a new feature in supabase-js that allows W3C Trace Context propagation, enabling client-side traces to connect with Supabase logs. This feature is available for JavaScript, Swift, Flutter, and Python, and supports various tracers like OpenTelemetry and Sentry. Feedback is requested from users who implement this feature.