[SOLVED] Is Prometheus an optimal option to monitor Proxmox?

[PythonTrader]

I have a Prometheus + Grafana setup in my home lab that is working well.

I have a Proxmox cluster that is consists of 3 nodes. I like to monitor my cluster.

I notice that Proxmox has no built-in support for Prometheus:




Considering that I already have a working Prometheus instance, should I use it for Proxmox or use what monitoring that Proxmox come with it?

 

[bitmover]

I've the same setup and also looking for a good solution.

There is a prometheus-exporter ( https://github.com/prometheus-pve/prometheus-pve-exporter ), but this does not feel right.

As there are already some existing Dashboards for Proxmox and InfluxDB available (https://grafana.com/grafana/dashboards/?dataSource=influxdb&search=proxmox) - so I am exploring the influxdb solution.

Initial testing looks good ( low IO , some working Dashboards ), but now i need to "understand" the influxdb-server config and make it secure.


One warning for others : I used an existing "graphite"-vm for one week for my 6 proxmox-nodes. During that week the graphite-VM was suffering from high IO.
Additionally when the graphite-vm was down, the Proxmox-WebUI became unesponsive ( showing only '?' and no VM-Names anymore ). Starting the graphite-VM or disabling the graphite-metics resolved the problem.

 

[PythonTrader]

I've the same setup and also looking for a good solution.

There is a prometheus-exporter ( https://github.com/prometheus-pve/prometheus-pve-exporter ), but this does not feel right.

As there are already some existing Dashboards for Proxmox and InfluxDB available (https://grafana.com/grafana/dashboards/?dataSource=influxdb&search=proxmox) - so I am exploring the influxdb solution.

Initial testing looks good ( low IO , some working Dashboards ), but now i need to "understand" the influxdb-server config and make it secure.


One warning for others : I used an existing "graphite"-vm for one week for my 6 proxmox-nodes. During that week the graphite-VM was suffering from high IO.
Additionally when the graphite-vm was down, the Proxmox-WebUI became unesponsive ( showing only '?' and no VM-Names anymore ). Starting the graphite-VM or disabling the graphite-metics resolved the problem.

Thank you for sharing your experience.

It is possible to have an instance of influxdb in a docker compose stack, so that it does not need much of setup, we need to provide volumens for storage and config.


I was hoping not to add yet another storage to what I already have (Loki and Prometheus )

 

[PythonTrader]

I've the same setup and also looking for a good solution.

There is a prometheus-exporter ( https://github.com/prometheus-pve/prometheus-pve-exporter ), but this does not feel right.

As there are already some existing Dashboards for Proxmox and InfluxDB available (https://grafana.com/grafana/dashboards/?dataSource=influxdb&search=proxmox) - so I am exploring the influxdb solution.

Initial testing looks good ( low IO , some working Dashboards ), but now i need to "understand" the influxdb-server config and make it secure.


One warning for others : I used an existing "graphite"-vm for one week for my 6 proxmox-nodes. During that week the graphite-VM was suffering from high IO.
Additionally when the graphite-vm was down, the Proxmox-WebUI became unesponsive ( showing only '?' and no VM-Names anymore ). Starting the graphite-VM or disabling the graphite-metics resolved the problem.

BTW, agree that prometheus-pve-exporter doesn't feel right.

I learned that we can have it on a separate machine, but not sure repercussions.

 

[deepcloud]

Hello,

I was considering

https://www.zabbix.com/ru/integrations/proxmox#proxmox
or
https://www.netdata.cloud/integrations/data-collection/containers-and-vms/proxmox-ve/

any thoughts