Connect client traces to your logs

Supabase-js now supports W3C Trace Context propagation, allowing client-side traces to share a trace_id with Supabase API Gateway and Edge Function logs for easier end-to-end debugging across browsers and backend services. Developers must configure their own OpenTelemetry tracer and provider, import the optional tracing entry point, enable tracePropagation when creating the Supabase client, and make requests within active spans. The integration sends standard traceparent, tracestate, and baggage headers only to Supabase and local development domains, while preserving bundle size and avoiding OpenTelemetry dependencies unless explicitly enabled. Trace IDs can also be included in Log Drains for correlation in external observability platforms such as Sentry, Datadog, Honeycomb, and Grafana. Limitations include no CDN or UMD support, support only for specified SDKs and log sources, and default respect for trace-sampling decisions. Users of earlier releases should upgrade to supabase-js 2.112.0 or newer because versions 2.106.0 through 2.111.x did not reliably send trace headers in bundled applications.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.