-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Agent causing CPU usage spikes in VM #59
Comments
Can you please provide a bit more info as to what the specs of the hypervisor are and what specs did you assign to the VM? Also, which Debian version was in the VM, and which Proxmox/Debian version was on the hypervisor? So we can set up a testing environment and try to reproduce the issue. Any other info that you might think would help will also be appreciated. Thank you. |
Sure. primary@mail:~$ uname -a
Linux mail 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux It's created using the official cloudinit-compatible image of Debian |
I also have the same problem. VM-OS is Debian 12 x64, the VM has been installed from Netinstall ISO. The VM is hosting a Mailcow-Mailserver inside several docker-containers. Agent is installed in Version 2.1.0 Kind regards |
Try increasing the agent's metrics collection interval as explained in our documentation: Also, please open a support ticket on our platform, including the monitor's name, so our techs can take a closer look at your metrics. Thank you. |
thanks for your comment. I am trying to set the Interval to 10s, see if CPU usage is going down. Kind regards |
After installing the agent in a Debian VM on Proxmox, I noticed that the VM periodically (every few seconds) spiked the CPU usage. After looking at htop, I confirmed this to be caused by the HetrixTools agent.
This is a graph of CPU% of the VM. The drop is after I uninstalled the agent.
I also have the agent installed on the host, where it doesn't seem to be doing this. Must be something specific to VMs.
The text was updated successfully, but these errors were encountered: