Open-Source Wikis

/

Supabase

/

Features

/

Logs and observability

supabase/supabase

Logs and observability

Studio's logs and observability surfaces unify product-wide telemetry: API logs, Auth logs, DB logs, Edge Function invocations, query performance, and dashboards.

Studio surfaces involved

Folder Purpose
components/interfaces/UnifiedLogs/ The cross-product logs explorer. The newest, canonical surface.
components/interfaces/Reports/ Saved reports and dashboards.
components/interfaces/QueryPerformance/ Top queries by time / calls / rows.
components/interfaces/QueryInsights/ Query analyzer.
components/interfaces/Observability/ Aggregated health and metrics.
components/interfaces/LogDrains/ External log-drain configuration.

Data layer

Logs- and metrics-related folders include:

  • data/logs/ — log queries (logs.totp.ts-style domain queries).
  • data/log-drains/ — drain CRUD.
  • data/reports/ — saved dashboards.
  • data/usage/, data/analytics/, data/service-status/, data/telemetry/ — per-domain metrics.

How it works

The runtime backend is Logflare (with Vector as the ingestion pipeline). Vector collects logs from every service and ships them into Logflare; Studio queries Logflare via the management API and displays the results.

graph LR
    Services[Postgres / Auth / PostgREST / Realtime / Storage / Edge Runtime]
    Vector[Vector]
    Logflare[Logflare]
    API[Mgmt API /logs endpoints]
    UI[UnifiedLogs / Reports / QueryPerformance]

    Services --> Vector
    Vector --> Logflare
    Logflare --> API
    API --> UI

In docker/docker-compose.yml the vector and logflare services run alongside the main stack; in self-host, you can configure log-drains in Studio to ship logs elsewhere.

Integration points

  • Vector + Logflare as the runtime backbone.
  • The platform's /logs/* endpoints (typed via packages/api-types).

Entry points for modification

  • Add a log query → extend data/logs/ and surface it via UnifiedLogs/.
  • Add a chart to a report → components/interfaces/Reports/ plus a query under data/reports/.
  • Add an external log-drain destination → upstream Logflare must support it; Studio just exposes the configuration UI under LogDrains/.

Built by Factory AutoWiki from public repository content. It is a generated preview for codebase exploration, not source-maintained documentation.

Logs and observability – Supabase wiki | Factory