Skip to content
This repository has been archived by the owner on Mar 12, 2021. It is now read-only.

expose domain state? #8

Open
vtolstov opened this issue Mar 12, 2018 · 6 comments
Open

expose domain state? #8

vtolstov opened this issue Mar 12, 2018 · 6 comments

Comments

@vtolstov
Copy link

vtolstov commented Mar 12, 2018

I'm use handmade script to detect crushed domains, does it possible to expose domain state with this exporter? So i can watch libvirt domain state ?

@BartVerc
Copy link
Member

I will discuss this option with my colleagues if we want to implement this. But I don't see why more metrics is a bad thing, so pull request is always welcome.

@BartVerc
Copy link
Member

I will fix this next week.

@vtolstov
Copy link
Author

Thanks!. I check node-exporter and thinks that libvirt exporter do the same thinkgs -
via command args we choose which metrics groups we want to expose:
domains
pools
volumes
networks
what do you think?

@stefreak
Copy link
Contributor

That only makes sense IMO if there is a reason not to collect the data (e.g. overhead)

@vtolstov
Copy link
Author

vtolstov commented Apr 1, 2018

@stefreak if we expose in/out traffic, cpu,memory, state, iops for each domain and each domain device (i ave nodes with 200 domains) i think that select what export will be useful.
Also for pools.

@beddari
Copy link

beddari commented Apr 12, 2019

We've patched this ourselves to get domain state, but I think there is enough users that want this now to warrant a tag and move to GetAllDomainStats()? What could help that happen?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants