We have some custom scripts that run on the hypervisors which poll: virsh dominfo virsh domiflist etc
The memory stats with "virsh dommemstat" are, AFAIK, not accurate since there's nothing triggering kvm / the vm to release unused memory. But all other virsh stuff works well for us. We don't record "load", but we do record CPU time. The "nova diagnostics" command can also be helpful. We have a custom policy in place to allow users to query their own instances. I think a few others are doing this as well -- there was a past discussion about it. Hope that helps, Joe On Thu, Nov 17, 2016 at 9:57 AM, Jean-Philippe Methot < [email protected]> wrote: > Hi, > > We are currently exploring monitoring solutions for the VMs we deploy for > our customers in production. What I have been asked to deploy would be > something akin to how you can see openvz container usage: you get memory > usage, bandwidth, load and so forth for each container. > > I know that ceilometer may be an option, but I believe operators use all > kind of tools for their own ressource usage monitoring. So what do you > people use? > > (For this use case, we're looking for something that can be used without > installing an agent in the VM, which makes it impossible to get a VM's load > metric. I would be satisfied with cpu/memory/network/io metrics though.) > > > > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
