The Cloud Metrics API is not available in self-hosted deployments. Each service in the Docker Compose stack exposes metrics independently — some are on by default (Supavisor, Realtime), some require environment variables to activate (Auth, Kong, Vector, Storage), and Postgres needs a sidecar exporter.
I traced each service's metrics path through the source code and tested everything end-to-end — sharing the results here as a proposed addition to docker/docs/.
Add a docker/docs/monitoring/ directory containing:
README.md — overview, service reference table, getting-started flowprometheus-pull.md — per-service detail (Supavisor, Realtime, Auth, Postgres, Kong, Vector): env vars to enable, source code references, key metrics, scrape config snippetsotel-push.md — Storage metrics via OpenTelemetry SDK (the /metrics route is multi-tenant-only, so OTel push is the only path in self-hosted)examples/ — drop-in config files: , , , , Jimin Byun proposes a new documentation addition for self-hosted deployments using Docker Compose. The proposal includes a monitoring guide with configuration files and instructions for enabling metrics across various services. The guide aims to help users set up monitoring using Prometheus and OpenTelemetry.
docker-compose.override.ymldocker-compose.metrics.ymlvictoriametrics/scrape.ymlvector/metrics.ymlotelcol/config.ymlAll endpoints were verified by reading the source code of each service (supabase/auth, supabase/storage, supabase/supavisor, supabase/realtime) and tested end-to-end against a live self-hosted instance using the unmodified docker/docker-compose.yml.
docker-compose.yml or any existing servicedocker/docker-compose.yml (Postgres 15.8.1.085, Kong 3.9.1, Auth 2.186.0, Storage 1.48.26, Supavisor 2.7.4, Realtime 2.76.5, Vector 0.53.0)