Exposes information gathered from Proxmox VE cluster for use by the Prometheus monitoring system
Full Changelog: https://github.com/prometheus-pve/prometheus-pve-exporter/compare/v3.2.5...v3.3.0
Full Changelog: https://github.com/prometheus-pve/prometheus-pve-exporter/compare/v3.2.4...v3.2.5
Full Changelog: https://github.com/prometheus-pve/prometheus-pve-exporter/compare/v3.2.2...v3.2.4
Full Changelog: https://github.com/prometheus-pve/prometheus-pve-exporter/compare/v3.2.1...v3.2.2
Full Changelog: https://github.com/prometheus-pve/prometheus-pve-exporter/compare/v3.2.0...v3.2.1
Full Changelog: https://github.com/prometheus-pve/prometheus-pve-exporter/compare/v3.1.0...v3.2.0
Full Changelog: https://github.com/prometheus-pve/prometheus-pve-exporter/compare/v3.0.2...v3.1.0
Note, this release contains breaking changes. Please read the release notes carefully before updating.
Thanks a lot @resmo for stepping up as a co-maintainer.
PR #180 introduced two new query parameters for the /pve endpoint allowing scrape jobs to specify which metrics are scraped:
The cluster query parameter governs whether cluster metrics are reported in the scrape. It defaults to 1 (cluster metrics are scraped by default). The query string cluster=0 can be used in order to disable reporting of cluster metrics.
The node query parameter specifies whether node metrics are reported from the given node. It defaults to 1 (node metrics are scraped by default). The query string node=0 can be used in order to disable reporting of node metrics.
This approach permits users to configure separate scrapes for cluster metrics (one for each cluster) and node metrics (one for each node). As a result, collection of node metrics is parallelized by prometheus automatically. Also it won't affect metrics of other nodes if one node is down.
Impact on existing deployments
The change has the following impact on existing deployments:
cluster and node url parameters are enabled by default.--no-collector.config: No effect. Even though both, the cluster and node url parameters are enabled by default, scrapes will still report exactly the same set of metrics as before since the config collector is disabled.--no-collector.config (or with --collector.config): Effect depends on the scraping strategy. Node metrics are only reported for those nodes being scraped. If all nodes are scraped in a cluster, then the upgrade to 3.0.0 has no effect on the set of metrics reported.tini binary was removed from the docker image. Use the docker --init flag instead.pve_exporter process is run as an unprivileged user by default. Use the docker --user flag to run pve_exporter as any user/group.Instead of positional arguments, pve_exporter now expects a config file to be specified via --config.file= flag and a custom address/port combination by --web.listen-address address flag. Users with custom config files or listen ports may have to adapt their startup scripts, docker compose recipes or systemd units.
Full Changelog: https://github.com/prometheus-pve/prometheus-pve-exporter/compare/v2.3.1...v3.0.2
Full Changelog: https://github.com/prometheus-pve/prometheus-pve-exporter/compare/v3.0.1...v3.0.2
Full Changelog: https://github.com/prometheus-pve/prometheus-pve-exporter/compare/v3.0.0...v3.0.1
Note, this release contains breaking changes. Please read the release notes carefully before updating.
Thanks a lot @resmo for stepping up as a co-maintainer.
PR #180 introduced two new query parameters for the /pve endpoint allowing scrape jobs to specify which metrics are scraped:
The cluster query parameter governs whether cluster metrics are reported in the scrape. It defaults to 1 (cluster metrics are scraped by default). The query string cluster=0 can be used in order to disable reporting of cluster metrics.
The node query parameter specifies whether node metrics are reported from the given node. It defaults to 1 (node metrics are scraped by default). The query string node=0 can be used in order to disable reporting of node metrics.
This approach permits users to configure separate scrapes for cluster metrics (one for each cluster) and node metrics (one for each node). As a result, collection of node metrics is parallelized by prometheus automatically. Also it won't affect metrics of other nodes if one node is down.
Impact on existing deployments
The change has the following impact on existing deployments:
cluster and node url parameters are enabled by default.--no-collector.config: No effect. Even though both, the cluster and node url parameters are enabled by default, scrapes will still report exactly the same set of metrics as before since the config collector is disabled.--no-collector.config (or with --collector.config): Effect depends on the scraping strategy. Node metrics are only reported for those nodes being scraped. If all nodes are scraped in a cluster, then the upgrade to 3.0.0 has no effect on the set of metrics reported.tini binary was removed from the docker image. Use the docker --init flag instead.pve_exporter process is run as an unprivileged user by default. Use the docker --user flag to run pve_exporter as any user/group.Instead of positional arguments, pve_exporter now expects a config file to be specified via --config.file= flag and a custom address/port combination by --web.listen-address address flag. Users with custom config files or listen ports may have to adapt their startup scripts, docker compose recipes or systemd units.
Full Changelog: https://github.com/prometheus-pve/prometheus-pve-exporter/compare/v2.3.1...v3.0.0