postgres_exporter VS node_exporter

🌟 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.

$ wget https://github.com/prometheus/node_exporter/releases/download/v1.7.0/node_exporter-1.7.0.linux-amd64.tar.gz $ tar -xzvf node_exporter-1.7.0.linux-amd64.tar.gz

Node Exporter

The Prometheus node_exporter can provide this information, doesn't require root. You could run it as a systemd user unit if you don't have root.

I personally find it best to learn through experimentation. Start with reading a bit about Prometheus and Grafana through their docs, and then familiarise yourself with setting up a local Prometheus + Grafana instance either locally or with docker using docker-compose, along with something to generate /metrics endpoint for Prometheus to scrape from such as a custom Prometheus exporter in Python or using Node Exporter.

Your best bet might be to fork node_exporter to get you more verbose socket stats: https://github.com/prometheus/node_exporter/blob/master/collector/sockstat_linux.go

I use Grafana + Prometheus + Node Exporter.

Crazy idea, can't NX devices run Docker? I wonder if the node_exporter would work.

Kubernetes itself will not notify you, the way I've seen people do this, is to use something like kube-state-metrics or node_exporter, export that to Prometheus (or preferrably VictoriaMetrics because Prometheus is terrible IMO), and then setup alarms on that with alertmanager or equivalent, or just look at dashboards regularly with Grafana. Realistically I recommend only setting alerts on disk usage and application/database latency. CPU and memory utilization isn't a great metric to alert on a lot of the time.

You may setup node exporter and collect metrics with prometheus for example. Its not quite "simple" way, but still you may find it useful.