Loading post…
SupabaseDiv AroraAnnouncement
Supabase Reports and Metrics
Summary
Supabase introduced a dedicated Reports section and updated project home pages to deliver observability across hosted Postgres projects and complementary services. Because developers can run unconstrained database queries and custom workloads, monitoring both project-level service usage and underlying infrastructure metrics is essential. The new dashboard displays one month of historical data, including CPU and memory usage alongside request volumes for Database, Auth, and Storage APIs. To collect metrics across hundreds of thousands of targets without high latency, Supabase implemented a federated monitoring architecture running regional Prometheus instances that scrape local exporters and aggregate subsets into a central VictoriaMetrics instance. All project databases now also launch with the pg_stat_statements extension enabled for future query statistics.
Context
Supabase provisions a Postgres cluster alongside services like PostgREST, Auth, Storage, and Realtime for each project. Because users have liberal access to run custom workloads and raw database connections, they risk triggering failure scenarios or resource bottlenecks that require detailed observability to diagnose and optimize.
Approach / What changed
Supabase introduced a Reports dashboard and updated project home pages displaying system and service metrics. To handle scraping hundreds of thousands of targets, Supabase deploys a federated monitoring system with regional Prometheus instances scraping project exporters, with aggregate subsets forwarded to a central VictoriaMetrics instance.
Takeaways
Supabase utilizes a federated monitoring architecture where regional Prometheus instances scrape project exporters across geographic regions to shard data collection and reduce latency.
A centralized VictoriaMetrics instance aggregates a subset of regional monitoring data to enable cross-project cohort analysis, with regional collectors also transitioning to VictoriaMetrics.
All new Supabase Postgres databases are provisioned with pg_stat_statements enabled by default to lay the groundwork for query-level performance statistics.
Source and freshness
- Source
- supabase.com
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.