---
slug: 53230-correlated-logs
published: 2026-11-10
change_type: improvement
affected_products:
  - Observability
  - Studio
  - Auth
  - CLI
page: https://supabase.com/changelog/53230-correlated-logs
---

# Correlated Logs

Correlated Logs is now available in Beta. The Studio Logs tab now lets you connect log events using three meaningful identifiers: `requestId`, `traceId`, and `userId`.

## What's new

Every log item now has four tabs: a structured **Overview**, **Raw JSON**, and two contextual tabs that appear when relevant:

- **Timeline** — where a `requestId` is present, fetches all log items for that request and shows them as a timeline. You can select any item in the chain to see its details and navigate back to the full list.
- **User** — where a log item is associated with an authenticated user, shows their details and links directly to that user in Auth. From the Auth user page, you can view all their logs in the same unified view.

![Studio Logs User tab showing the user associated with a log event](https://changelog-nstyu96fo-supabase.vercel.app/assets/correlated-logs/studio-user-tab.png)

You can also filter the logs list by user attributes to see all log items for a specific user, in the same way you filter by `requestId` or `traceId`.

For AI agents using the Supabase MCP server, the `query_logs` tool supports the same identifiers. See [MCP debugging](https://supabase.com/docs/guides/ai-tools/mcp#debugging).

## How to use it

Open the [Logs tab](https://supabase.com/dashboard/project/_/logs) in your project dashboard and filter by `requestId`, `traceId`, or user attributes. Click into any log item to see the Timeline or User tab where available.

To send a `traceId` from your application, see [client-side tracing](https://supabase.com/docs/guides/observability/client-side-tracing).

## Logs in CLI v3

Inspect hosted logs in your terminal:

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

Filter by service, severity, or time range. Use `--from` and `--to` for fixed UTC bounds.

![CLI log explorer showing local database events](https://supabase.com/docs/img/guides/observability/cli-logs/explorer.jpg)

In an interactive terminal, use the up and down arrows to select a row, Enter to inspect it, `C` to copy the full record as JSON, and `L` to load newer logs on demand.

For scripts and agents, `--output-format json` and `--output-format stream-json` read once and exit. Query hosted logs with `--sql` or load SQL with `--file`.

The command defaults to local logs, which require the experimental stack runtime.

Read the [CLI logs guide](https://supabase.com/docs/guides/observability/cli-logs) for setup and examples.

## Why we built this

When something goes wrong, the signal is spread across log items from different services, and tracking it back to a specific request or user means cross-referencing timestamps by hand. These connections should be a click away.

This is a Beta release. Try it and share feedback in the GitHub Discussion below.