Supabase APINew featureinfo

Supabase launches Correlated Logs Beta with requestId traceId and userId linking

Detected
Nov 11, 2026
Effective
Nov 10, 2026
Confidence
90%

What changed

Supabase has launched Correlated Logs in Beta, allowing users to connect log events via requestId, traceId, and userId in the Studio Logs tab. The feature also includes new CLI v3 log inspection capabilities and MCP server support via the query_logs tool.

What to do

To leverage traceId correlation, instrument your application with client-side tracing as described in Supabase's tracing guide. Use the updated CLI v3 supabase logs command for terminal-based log inspection.

Affected

endpoint: query_logs (MCP tool)param: requestIdparam: traceIdparam: userIdparam: --output-formatparam: --sqlparam: --file

Source: supabase.com (Supabase's own page, checked by Breakwatch)

Is your code affected?

Search your repositories for the Supabase SDK and the names above:

npm: @supabase/supabase-jspip: supabaseruby: supabasego: github.com/supabase-community/supabase-gorust: postgrest

Or let Breakwatch do it: connect a repo and see which files call Supabase, then get the next change as an alert pointing at those files. Check a repo free

Get Supabase API changes by email

Once a week: the breaking changes and upcoming deadlines for Supabase, each linked to the vendor's own page. Free, no account. One-click unsubscribe.

More Supabase API changes

Every Supabase API change →