On 9/29/25 3:17 PM, Sean Mooney wrote:
On 29/09/2025 13:42, Nguyễn Hữu Khôi wrote:
Hello.
I see that this exporter looks like it collects a lot of information such as projectname, username or flavor of metrics but it looks not popular. It could help us build a very useful dashboard.
https://github.com/zhangjianweibj/prometheus-libvirt-exporter
there is also https://github.com/inovex/prometheus-libvirt-exporter
which is a fork of it and https://github.com/kumina/libvirt_exporter which is what was packaged by distos like debian in the past
It's actually a fork of https://github.com/zhangjianweibj/prometheus-libvirt-exporter .
https://salsa.debian.org/go-team/packages/prometheus-libvirt-exporter
so there have been a couple of competing implementation and no clear winner that im aware of between the 3
Yes, indeed it's a little sad there is this this diverse landscape. A de-facto standard exporter on top of the libvirt API should be possible. Only after not seeing such an exporter we actually pushed forward with https://github.com/inovex/prometheus-libvirt-exporter . We did so with the intention to create a robust, flexible and portable exporter for most libvirt needs. Also export of OpenStack-specific labels was implemented, best-practices in regards to metric naming and dealing with labels via info-metrics were followed. We also received some issues and PRs already, some even involving Libvirt maintainers: https://github.com/inovex/prometheus-libvirt-exporter/pull/77 After all we intend to maintain and keep this exporter alive - but please send bugs, send patches! But we also more than happily would donate the exporter to the Prometheus Community. See our issue suggesting this: https://github.com/prometheus-community/community/issues/50 Regards Christian