Health Check Advisors
Find which Supabase service has a high server error rate.
Stage:
General Availability
Available on self-hosted:
N/A
With Health Check Advisors, you know which Supabase service to look at first. Run the checks for Auth, Storage, Edge Functions, and the Data API from the Health tab or the Management API. When you run them, each service whose error rate stays high returns a result.
Key benefits
- Know where to look: With one check per service, you see which one has a high error rate before you open a log.
- Sort by severity: Every result has a severity level, and you can start with the worst one.
- Go straight to the logs: In the dashboard, View logs on any result opens the API Gateway logs, so you can check the errors yourself.
- Trust an empty result: No result means every check ran and found no high error rate.
- Give your agent a starting point: Over the Management API, your agent gets the results you see in the dashboard.
- Read Health like the other advisors: Health results use the same fields as Security and Performance in the dashboard and the Management API, so all three read the same way.
When to use Health Check Advisors
- Your app throws server errors and you don't know which service is behind them (one check per service, run on demand)
- After a deploy, you want to see if any service's server errors stay high (run the checks from the Health tab)
- Your agent needs to know which service to debug first (the same checks over the Management API)
How it works
The checks measure the server error (5xx) rate in recent request logs for each service. The error rate has to stay high over a period, so a result can take a while to clear after a fix. Results are cached, and quick repeat calls return the same snapshot. Over the Management API, a check that could not run says so.
Get started
- In the dashboard, open Advisors, then Health.
- From the Management API, call
POST /v2/projects/{ref}/advisors/run(API reference). - Read the Advisors docs.