postgres_exporter VS supabase

🌟 Support on GitHub Website: http://prometheus.io/community

An easy way forward would be to export it as a metric through something like https://github.com/prometheus-community/postgres_exporter and then set up an alert on the metric reporting >= 1.

We use postgres as RDBMS for our database needs and if you guys are already using postgres_exporter(https://github.com/prometheus-community/postgres_exporter) for exporting PostgreSQL server metrics to prometheus, then you can surely give coroot-pg-agent a try.

It’s not that simple…https://github.com/prometheus-community/postgres_exporter :)

New server and want a basic config for a production server? (I'm assuming brand new app here, no prior monitoring and knowledge on what to tune.)

Use this to get the values you need https://pgtune.leopard.in.ua/#/ .

This saved me a lot of headaches, and it just gets the server into a good enough state from which you can observe and optimise later.

I'd also add in monitoring early, add a Prometheus exporter https://github.com/prometheus-community/postgres_exporter and alerts https://awesome-prometheus-alerts.grep.to/rules#postgresql . There are a few Grafana dashboards available for the prometheus exporter, start with those.

I’m setting up some monitoring for a PostgreSQL instance and came across two seemingly mature projects for Prometheus monitoring, those being postgres_exporter and pg_exporter . From the outside it looks like postgres_exporter is linked from the Prometheus pages, but has fewer recent updates, and pg_exporter has a smaller user base but a more active development community.

PostgreSQL monitoring with Prometheus is an easy thing to do thanks to the PostgreSQL Exporter.

Thanks, that is probably a better fit. I was looking to use this part of the PostgreSQL exporter: https://github.com/prometheus-community/postgres_exporter/blob/master/queries.yaml and just not care about the metrics about Postgres itself.

The postgres_exporter provides the data about the state of replication. Then you have rules like these to validate the data.

I didn't really give much thought as to which backend I would use. I already had 2 projects in Supabase (BOXCUT & MineWork), but also a few projects in Firebase too. I was more concerned at the time at actually building the product.

Sign up for SupaBase: Head over to SupaBase and sign up. Create a new workspace and project with your preferred names.

Setting up Supabase Create a new Supabase project, and get the connection string for the database from settings > database.

Supabase (start for free)

Built with Supabase, Astro, Unreal Speech, Stable Diffusion, Replicate, Metropolitan Museum of Art

Supabase will be used for storing article data in the database and the cover image of the article in storage. Chakra UI will be used to provide style to the elements. By using both, we can build the blog with ease.

For AutoRepurpose, I opted for Supabase as the backbone of the backend. It has reliably supported Penelope AI, which garnered over 15k users in 2022 without any issues.

Semantic search demo

1. Create a new Supabase project: Visit Supabase and create a new project.

Supabase positions itself as the "open source Firebase alternative." It was founded in 2020 and is a developer-friendly serverless database platform that supports over 20 frameworks, including popular tools like Next.js, React, Nuxt, Svelte, Flutter, and Vue.