Rebuilding Postgres Metrics on Self-Hosted VictoriaMetrics with Zero Downtime
Xata successfully migrated its PostgreSQL metrics to a self-hosted VictoriaMetrics stack over six weeks without any downtime for users. The transition was driven by the need for improved performance, scalability, and cost-effectiveness in their observability infrastructure. The new setup allows for metrics to be processed locally within each cell, enhancing efficiency and reducing reliance on external vendors.
- ▪Xata's PostgreSQL metrics were previously managed through a third-party observability vendor.
- ▪The migration to VictoriaMetrics was completed without any visible downtime for customers.
- ▪The new architecture allows for metrics to be processed locally within each cell, improving performance and reducing costs.
Opening excerpt (first ~120 words) tap to expand
Back to BlogHow we rebuilt PostgreSQL branch metrics on VictoriaMetrics, per cellHow we rebuilt Xata's PostgreSQL branch metrics on a self-hosted VictoriaMetrics stack in six weeks, with zero user-visible downtime.By:Alexis RicoPublished:Jun 2, 2026Reading time:6 min readBack to BlogTable of contents01. The starting picture02. Why we moved03. Why VictoriaMetrics04. The new shape05. The cutover06. What stuck with us07. What's nextTagsXataFeaturedDatabase branching in the age of AIInside Xatastor: ZFS + NVMe-oF for Postgres databasesIntroducing Xata OSS: Postgres platform with branchingEvery Xata branch is backed by real PostgreSQL. In the web console, each branch has a metrics view: CPU, memory, connections, disk I/O, network, WAL sync time, replication lag, database size.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Xata.
Discussion
0 commentsMore from Xata
