Metrics API
Every Supabase project exposes a Prometheus-compatible Metrics API endpoint that surfaces ~200 Postgres performance and health series. You can scrape it into any observability stack to power custom dashboards, alerting rules, or long-term retention that goes beyond what Supabase Studio provides out of the box.
Chart a subset of the same window in Studio Reports. Use this page when you want the Prometheus-compatible scrape endpoint.
The Metrics API is currently in beta. Metric names and labels might evolve as we expand the dataset, and the feature is not available in self-hosted Supabase instances.
What you can do with the Metrics API
- Stream database CPU, IO, WAL, connection, and query stats into Prometheus-compatible systems.
- Combine Supabase metrics with application signals in Grafana, Datadog, or any other observability vendor.
- For Grafana, you can use the Grafana Cloud integration in the Supabase Dashboard to get a configured instance and prebuilt dashboard in one click.
- Reuse our supabase-grafana dashboard JSON to bootstrap over 200 ready-made charts.
- Build your own alerting policies (right-sizing, saturation detection, index regression, and more).
What you can do with the Metrics API
Every Supabase project exposes a metrics feed at https://<project-ref>.supabase.co/customer/v1/privileged/metrics. Replace <project-ref> with the identifier from your project URL or from the dashboard sidebar.
- Copy your project reference and confirm the base URL using the helper below.
- Configure your collector to scrape once per minute. The endpoint already emits the full set of metrics on each request.
- Authenticate with HTTP Basic Auth:
- Username:
service_role - Password: a Secret API key (
sb_secret_...). You can create/copy it in Project Settings → API Keys. For more context, see API keys.
To test locally, run curl with your Secret API key:
curl <project-url>/customer/v1/privileged/metrics \--user 'service_role:sb_secret_...'You can provision long-lived automation tokens in two ways:
- Create an account access token once at Account Settings > Access Tokens and reuse it wherever you configure observability tooling.
- Optional: programmatically exchange an access token for project API keys via the Management API.
# (Optional) Exchange an account access token for project API keysexport SUPABASE_ACCESS_TOKEN="your-access-token"export PROJECT_REF="your-project-ref"curl -H "Authorization: Bearer $SUPABASE_ACCESS_TOKEN" \"https://api.supabase.com/v1/projects/$PROJECT_REF/api-keys?reveal=true"Choose your monitoring stack
Pick the workflow that best matches your tooling. Cards link to Supabase-authored guides or vendor integration docs, and some include a “Community” pill when there’s an accompanying vendor reference.
Grafana Cloud (SaaS)
Grafana + self-hosted Prometheus
Datadog
Elastic
Vendor-agnostic / BYO Prometheus

Additional resources
- Supabase Grafana repository for dashboard JSON and alert examples.
- Grafana Cloud integration for the one-click setup, plus Grafana’s integration reference for manual configuration.
- Datadog’s Supabase integration doc (community-maintained, built on this Metrics API).
- Elastic’s Supabase integration doc (community-maintained).
- Log Drains for exporting event-based telemetry alongside metrics.
- Query Performance report for built-in visualizations based on the same underlying metrics.