Observability
Use project data to understand what is happening, investigate issues, and give an agent repeatable checks to run.
Read project data #
Query logs for events, inspect database statistics, or review advisor findings. Use Reports to visualize signals and the Metrics API to export them.
- Query ClickHouse events through MCP, the API, or Explorer.
Query logs with SQL
- Filter, inspect, and export events in the unified Logs view.
Logs in Studio
- Look up sources, ClickHouse query fields, and capture limits.
Log sources and fields
- Scrape Prometheus-compatible database metrics, or chart a subset in Reports.
Metrics API
- Inspect live Postgres stats from the CLI, Explorer, or MCP.
Inspect the database
- Pull security and performance findings from Studio, MCP, the CLI, or the API.
Advisors
- Studio dashboards for API, Auth, Storage, Realtime, and database signals.
Reports
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.
Hire an agent#
Give an agent recurring checks to run and findings to report. Set up an agent with read-only access to your project.
- Once per dayRun all four checks — health, security, performance, and capacity — in one daily pass.
Generalist
- Once per hourCheck API and Auth server errors and connection pressure.
Health monitor
- Once per dayReview advisor findings and authorization failures.
Security monitor
- Once per hourReview sessions, query regressions, and performance advisors.
Performance monitor
- Once each morningTrack sizes, connections, request growth, and supported forecasts.
Capacity monitor
Configure and export#
Record additional events or send telemetry to your monitoring tools.