Hello, As far as ( know metrics in the UI just show host's resourcess utilisation by the VMM. Actual resource usage of a VM can only be monitored from inside the guest OS. This is a normal behaviour of a fully virtualized hypervisors like KVM/QENU.
Regards. On Fri, 16 Aug 2024, 01:49 Nathan Gleason, <[email protected]> wrote: > Hello, > > We’ve recently upgraded Cloudstack from 4.18.1.0 to 4.19.1.0, then to > 4.19.1.1. While testing Autoscale we’ve found that a ScaleUp policy for > “VM CPU - average percentage” does not work. We run cpuburn on the VM to > load the CPU to 100%. We see the metrics in the UI as well as in the > autoscale_vmgroup_statistics table. But scale up never happens. We’ve set > the threshold anywhere from 1% to 50% but it does not work. We have > restarted cloudstack-mangement, cloudstack-agent, libvirtd, etc… Has > anyone encountered this? > > This may be unrelated but we have also noticed that memory metrics for all > of the VMs are incorrect. We load the memory with memtester and while the > VM shows the memory usage properly, the metrics do not. We found this > while testing “VM Memory - average percentage” in ScaleUp policies. > > Versions: > > OS: Ubuntu 22.04 > Cloudstack: 4.19.1.1 > Hypervisor: KVM > > Libvirt: > Compiled against library: libvirt 8.0.0 > Using library: libvirt 8.0.0 > Using API: QEMU 8.0.0 > Running hypervisor: QEMU 6.2.0 > > Thank you, > Nathan
