---
title: "Connect client traces to your logs"
description: "supabase-js now supports W3C Trace Context propagation so a client trace can share its trace_id with Supabase API Gateway and Edge Function logs. Previously, browser and server records had no shared identifier, making cross-boundary debugging depend on manually aligning timestamps. When tracePropagation is enabled, the SDK attaches traceparent, tracestate, and baggage to requests for Supabase domains; Supabase preserves the trace_id in generated logs, and W3C-compliant tracers such as OpenTelemetry, Sentry, Datadog, Honeycomb, or Grafana can continue the trace server-side. The setup requires a separately configured tracer, the tracing entry-point import, an active span, and a registered TracerProvider; propagation is sampling-aware by default, adds no OpenTelemetry code to the main bundle, and is available in supabase-js 2.112.0 or later, with CDN/UMD builds excluded."
---

# Connect client traces to your logs

[Supabase](https://yomu.fyi/company/supabase) · katerina\_skroumpelou, steven\_eubank · Aug 18, 2026

**Type:** Announcement

## Summary

supabase-js now supports W3C Trace Context propagation so a client trace can share its trace\_id with Supabase API Gateway and Edge Function logs. Previously, browser and server records had no shared identifier, making cross-boundary debugging depend on manually aligning timestamps. When tracePropagation is enabled, the SDK attaches traceparent, tracestate, and baggage to requests for Supabase domains; Supabase preserves the trace\_id in generated logs, and W3C-compliant tracers such as OpenTelemetry, Sentry, Datadog, Honeycomb, or Grafana can continue the trace server-side. The setup requires a separately configured tracer, the tracing entry-point import, an active span, and a registered TracerProvider; propagation is sampling-aware by default, adds no OpenTelemetry code to the main bundle, and is available in supabase-js 2.112.0 or later, with CDN/UMD builds excluded.

## Context

Client traces and Supabase logs previously had no shared identifier, so debugging a request across the browser and backend required manually aligning timestamps.

## Approach / What changed

The SDK can propagate W3C Trace Context when tracePropagation is enabled. It sends traceparent, tracestate, and baggage to Supabase domains, while Supabase adds the same trace\_id to API Gateway and Edge Function logs. Applications must configure their own tracer, load the tracing entry point, and make requests inside an active span.

## Takeaways

- tracePropagation sends traceparent, tracestate, and baggage only to Supabase project hosts, Supabase domains, and listed local development hosts, not third-party hosts.
- The integration requires an active span and a registered TracerProvider; without them, the SDK silently performs no propagation. Sampling decisions are respected unless respectSamplingDecision is set to false.
- The tracing integration is excluded from the main supabase-js bundle and is unavailable in CDN/UMD builds. Bundled applications using versions 2.106.0 through 2.111.x should upgrade to 2.112.0 or later.

**Tags:** [Monitoring](https://yomu.fyi/topic/monitoring), [Observability](https://yomu.fyi/topic/observability)

- Source: [Supabase](https://supabase.com/blog/connect-client-traces-to-your-logs)
- Source URL: https://supabase.com/blog/connect-client-traces-to-your-logs
- Ingested by Yomu: 2026-08-30T12:47:22.182Z

[Read original post](https://supabase.com/blog/connect-client-traces-to-your-logs)