Observability

Use project data to understand what is happening, investigate issues, and give an agent repeatable checks to run.

Read project data [#metrics-api]

Query logs for events, inspect database statistics, or review advisor findings. Use Reports to visualize signals and the Metrics API to export them.

• Query logs with SQL: Query ClickHouse events through MCP, the API, or Explorer.
• Logs in Studio: Filter, inspect, and export events in the unified Logs view.
• Log sources and fields: Look up sources, ClickHouse query fields, and capture limits.
• Metrics API: Scrape Prometheus-compatible database metrics, or chart a subset in Reports.
• Inspect the database: Inspect live Postgres stats from the CLI, Explorer, or MCP.
• Advisors: Pull security and performance findings from Studio, MCP, the CLI, or the API.
• Reports: Studio dashboards for API, Auth, Storage, Realtime, and database signals.

Detect and diagnose

Run detection checks to identify health, security, performance, or capacity issues. Take the resulting error code, time window, or affected object to the troubleshooting guides, then rerun the check after a fix.

Agent prompts

Give an agent a prompt to check your project and report issues to fix. See the prompts and run them with read-only access to your project.

Configure and export

Record additional events or send telemetry to your monitoring tools.

• Configure logging: Record additional Postgres and Realtime events.
• Log drains: Send project logs to your own destination.
• Client-side tracing: Propagate W3C trace context from the client through Supabase services.
• Sentry integration: Capture supabase-js errors and spans in Sentry.