Closed znachtman closed 9 months ago
Also for reference, I've reviewed this item in detail: https://github.com/prometheus-pve/prometheus-pve-exporter/issues/156.
I'm also using the grafana dashboard referenced in the readme https://grafana.com/grafana/dashboards/10347-proxmox-via-prometheus/
. At the moment, I'm getting a lot of duplicate data, as each node is returning cluster wide metrics. I'm hoping converting the queries to cluster=0&node=1
fixes this issue on the dashboard side, if I can get query parameters to return node-level data.
This is expected behavior. The only node
metric is pve_onboot_status
. All other metrics are cluster
metrics.
When I access
http://pve-exporter:9221/pve?target=nodename.foo&node=1&cluster=0
I only get:
Additional information:
prompve/prometheus-pve-exporter:latest
(I've also tried other 3.x images).tail -n 400 /var/log/pveproxy/access.log
on one of the proxmox nodes). See below for an example of the access logs on the PVE node...Nothing is in the
prompve/prometheus-pve-exporter
logs, outside of TLS warnings that are generated when accessing various proxmox nodes (e.g./opt/prometheus-pve-exporter/lib/python3.11/site-packages/urllib3/connectionpool.py:1099: InsecureRequestWarning: Unverified HTTPS request is being made to host...
).I'm able to access cluster metrics just fine.
It appears the APIs are getting queried, data is correctly getting returned to PVE exporter (from proxmox); however, it looks like that data is not being returned from PVE exporter as far as I can tell.