Aleksei Zakharov

Hi, thanks for your PR! As I can see from [libvirt documentation](https://libvirt.org/html/libvirt-libvirt-host.html#virNodeGetInfo): ``` Use of this API is strongly discouraged as the information provided is not guaranteed to be accurate...

Thanks for the PR! Unfortunately, I didn't have time to check how it works right now. But it seems like a good starting point. I see two huge problems with...

Hi! This dashboard isn't compatible with this libvirt-exporter. Dashboard is managed by other guys. I think it's possible to create some demo dashboard for this libvirt-exporter. Please, write in English...

Hi, thanks for the suggestion! There's a problem with this exporter: it's not a statically built binary. There's no good way to build it statically, because libvirt-go doesn't support that....

@Ubun1 thanks for pointing that out. Yes, this might be a way to go. But I assume it is a huge rewrite and I'm not sure if it supports all...

@gtherond , I've released version 2.2.1 which is available on [dockerhub](https://hub.docker.com/repository/docker/alekseizakharov/libvirt-exporter).

@Ubun1 thanks a lot for this! Would you be able to prepare a PR with these changes? btw, what version of libvirtd do you use during tests?

We're using bonding too, it would be great to add `Aggregator ID` for every link as a gauge(/sys/class/net/bond0/lower_eth3/bonding_slave/ad_aggregator_id): `node_bonding_aggregator_id{master_device="bond0", device="eth3"} 1` Different aggregator ID's might be, for example, if switch...

@frittentheke, sorry, i don't support this project actively anymore, as i don't work on cloud infrastructure:( New maintaner is @k3nny0ne, i hope he can help here

Unfortunately I work only with prometheus, not statsd/m3db/etc. Can't help with them 😞 [Here](https://github.com/statsd/statsd/blob/master/docs/metric_types.md#timing) there's something about "bins" in statsd. Probably it's the same as prometheus histograms. I couldn't find...