Skip to content

Supabase Studio can now connect logs by request or user

Correlated Logs links events by requestId, traceId or userId in Studio, and the CLI gets a terminal log explorer with SQL queries and JSON export.

Source: Supabase

Supabase released Correlated Logs in beta on 10 November, adding a way to follow one request, trace or user across every log Supabase captures. In Studio’s Logs tab, each log item now has four views: a structured Overview, Raw JSON, a Timeline that appears when a requestId is present and lines up every event for that request, and a User tab that links straight through to Auth when the log is tied to an authenticated user.

The CLI gets the same correlation. CLI v3 adds a terminal log explorer you can filter by service, level and time window, or query directly with SQL:

supabase logs --remote --service postgres --level error --since 30m

Add --sql or --file to run a saved query against hosted logs, and --output-format json to pipe results elsewhere. The Supabase MCP server’s query_logs tool uses the same requestId, traceId and userId fields.

Why it matters: debugging a Supabase app usually means jumping between Studio tabs and a log export to piece a request back together. Correlated Logs and the CLI explorer put that history in one place, in the terminal if that’s where you’d rather work.

The caveat: it’s beta, and local logs still need the experimental stack runtime enabled.

Share

Related reading

More from The Wire

All briefs