# Studio Logs and Reports pages are missing

> Supabase Studio's Logs, log explorer and Reports pages aren't available on SupaHost. Where to find function logs, slow queries, service logs and usage instead.

Source: https://supahost.app/kb/studio-logs-reports-missing · Updated 2026-11-11

## What you see

In Supabase Studio, the Logs section, the log explorer and the Reports pages (the API, Auth, Database and Storage charts) aren't available. The project's **Logs** tab in the SupaHost dashboard says searchable logs are coming soon.

## Why it happens

On Supabase Cloud, those pages are powered by a separate analytics and logging pipeline that collects logs from every service. SupaHost runs the open-source Studio without that pipeline, so the pages that depend on it are switched off. A searchable log explorer in the SupaHost dashboard is planned but not available yet.

## Where to look instead

| You want | Use |
|---|---|
| Edge Function output, errors and requests | *Dashboard → your project → **Functions** tab → Logs*, filtered by function and refreshed every 10 seconds. Or `get_edge_function_logs` over MCP. |
| Cron job results | *Dashboard → your project → **Cron** tab → **Recent runs***, or `cron.job_run_details` in SQL |
| Database webhook and pg_net results | `net._http_response` in SQL ([how](/kb/webhook-debugging)) |
| Slow or frequent queries | `pg_stat_statements` in Studio's SQL editor |
| Auth, REST, Storage and gateway logs | `sudo supahost-logs` over SSH (Business and Enterprise) |
| Database size, storage and egress | *Dashboard → **Usage & billing*** |
| Who changed what | *Dashboard → **Activity*** |

### Slow queries with pg_stat_statements

This shows where the database spends its time, which is most of what the Database report is for:

```sql
select
  round(total_exec_time::numeric, 1) as total_ms,
  calls,
  round(mean_exec_time::numeric, 2) as mean_ms,
  left(query, 120) as query
from pg_stat_statements
order by total_exec_time desc
limit 15;
```

If you get a permission error, see [insufficient privilege on pg_stat_statements](/kb/pg-stat-statements-privilege). The statistics cover the whole Postgres server, so filter by `dbid` if you only want one project's queries.

### Service logs over SSH (Business and Enterprise)

```bash
ssh supahost@acme.supahost.space
sudo supahost-logs app-one auth --follow
```

Replace `auth` with `rest`, `storage`, `functions` or `http` (the gateway's access log). Without `--follow` you get the last 200 lines. Add your SSH key first under *Dashboard → your project → **Connect** → **SSH & CLI***.

## On SupaHost

- Logs inside Studio are disabled. The rest of Studio (table editor, SQL editor, Auth users, Storage, policies, database tools, API docs) works as normal.
- Function logs are kept by size, not time: roughly the most recent couple of megabytes per project.
- On Builder or Pro, if you're stuck on an Auth or Data API problem, log the full error your app receives (status, message and response body) and email support with it, the project name and the time in UTC. See [writing a support request](/kb/support-requests).

## Related

- [Logs and debugging](/docs/functions/logs)
- [Monitoring, health checks and alerts](/docs/platform/monitoring)
- [SSH access and direct Postgres](/docs/platform/ssh)
- [Query performance and EXPLAIN](/docs/database/query-performance)