Thanks Wei,
I enabled DEBUG in the log4j and it’s not returning any error o warn, I’m using
the utility “stress –cpu 4” to simulate busy cpu but nothing happens on a 1%
threshold.
2023-06-01 13:19:22,690 DEBUG [cloud.agent.Agent] (agentRequest-Handler-4:null)
(logid:7b03dbe0)
Hi Ricardo,
ACS gets the VM statistics (including cpu, memory, network, disk
statistics) by sending GetVmStatsCommand to the kvm host, and getting the
answer GetVmStatsAnswer from the kvm host.
Can you check agent.log if there are errors ?
For example, I cannot get memory statistics due to error
Here's what I see
2023-05-30 15:08:35,483 INFO [resource.virtualnetwork.VirtualRoutingResource]
(agentRequest-Handler-4:null) (logid:bff92bbe) Fetching health check result for
169.254.82.180 and executing fresh checks: **false**
2023-05-30 15:08:35,884 INFO
Hi Ricardo,
It looks the CPU usage (raw_value) is 0 . Can you check the agent.log ?
INACTIVE means there are some changes with the AS vm group at that time,
for example create/enable/disable/scaleup/scaledown.
-Wei
On Tuesday, 30 May 2023, Ricardo Pertuz
wrote:
> Hi Wei,
>
> Thanks for
Hi Wei,
Thanks for replying, my threshold is 5% just to check and the ACS metrics says
28% in usage
looks like no error in logs, however I see this message
**success: Creating file in VR, with ip: 169.254.89.121, file:
monitor_service.json.ec3acdd8-b1c1-4603-9fde-79eece662390","null -
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
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
