Hi Ricardo, We (including dev and qa) have done intensive testing with different hypervisors and scenarios. You may hit a bug, but more likely a misconfiguration issue.
You can check by the following steps: (1) check database table "autoscale_vmgroup_statistics" to see if the metrics have been collected with correct value and frequency. (2) check management-server.log to see if cloudstack checks the metrics periodically. I suggest you to test with small threshold. The cpu usage is collected from the kvm hypervisor , calculated from the cpu time on the vm, which might have big difference as you thought. -Wei On Tuesday, 30 May 2023, Ricardo Pertuz <[email protected]> wrote: > Hi, > > On our env with ACS 4.18 KVM hypervisor, we have configured an autoscale > vm group with cpu average counter, however it does not trigger the scale up > even the threshold have been reached longer than the stipulated. What > should we check? are we missing something? > > Min Instances 1 (always remains in 1 instance) > Max Instances 3 > > > Ricardo Pertuz
