g14wxz/supabase-observability-metrics
Configures Prometheus scraping, log drains, and observability for Supabase infrastructure monitoring.
97
97%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
index.mddocs/
Supabase Observability Metrics
Configures Prometheus scraping, log drains, and observability for Supabase infrastructure monitoring.
Overview
This tile sets up a Prometheus scrape job targeting the Supabase privileged metrics endpoint and configures log drain pipelines for API, Postgres, and Auth log sources. It establishes monitoring coverage for four required domains: API response times, database connection pool usage, auth token issuance rates, and storage operation latency. Alert baselines are defined for latency and saturation thresholds.
Reference
Metrics Endpoint
https://<project-ref>.supabase.co/customer/v1/privileged/metricsAuthenticated via Authorization: Bearer <service_role_key>.
Required Metric Families
| Family | Prometheus Prefix | Covers |
|---|---|---|
| API response times | http_request_duration_seconds | Gateway latency |
| Connection pool | pgbouncer_pools_* | PgBouncer saturation |
| Auth issuance | gotrue_* | Token generation rates |
| Storage latency | storage_* | Object operation times |
Alert Thresholds
| Metric | WARNING | CRITICAL |
|---|---|---|
| API p95 latency | > 2s | > 5s |
| Connection pool saturation | > 80% | > 95% |
| Auth error rate | > 5% | — |
Dependencies
- supabase-mcp-verification (root prerequisite) — MUST pass before any observability configuration.
- Supabase Pro plan or higher — metrics endpoint is unavailable on Free tier.
- Prometheus server — MUST be reachable and writable for scrape job configuration.
Composition Position
- Stage: operations-monitoring
- Priority: HIGH
- Runs after MCP verification and infrastructure provisioning. Produces metrics and alerts consumed by dashboarding and incident-response tiles.