# Supabase — Connect client traces to your logs

- Company: Supabase (supabase.com)
- Announced: 2026-08-18
- Category: capability-change
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://supabase.com/blog/connect-client-traces-to-your-logs
- Record: https://forck.live/items/21272-connect-client-traces-to-your-logs
- Subject: Supabase

Supabase added W3C Trace Context propagation to supabase-js, allowing client trace IDs to flow into API Gateway and Edge Function logs. When enabled, the SDK attaches traceparent, tracestate, and baggage headers to Supabase requests, enabling end-to-end request tracing from browser to backend logs. The feature is also available in Swift, Flutter, and Python SDKs.

## Evidence

Verbatim from https://supabase.com/blog/connect-client-traces-to-your-logs:

> supabase-js now propagates W3C Trace Context to Supabase. Turn it on 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.

---

Record: https://forck.live/items/21272-connect-client-traces-to-your-logs
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md