Checkmk Community - Change scanning interval based on the type of service being monitored

[andreas-doehler (Andreas)]

@alessiottero

I am currently using the latest version of Checkmk Community (2.5.0), hosted in a Docker container, the host VM is a machine based on the Ubuntu Server 24.04 cloud image.

I’m monitoring 17 hosts with about 300 services, even though the VM is very small (2 cores and 4 GB of RAM on a Proxmox host, which is a mini-PC with an Intel N100 processor), the load on the machine is very high, and I can’t get the service to run smoothly enough.

Here i would pay attention to the configuration of you monitoring core (Nagios). Nagios core inside Docker container is not so good. If you are already on a Proxmox host i would run the CMK as an LXC directly on Proxmox and not inside a container thats inside a VM.
If you habe only two core i would recommend to set the concurrent checks to a value of 2 or maximum 4 inside the Nagios core config.

Checks running in bursts causing OOM

There is an option but only on the command line → ~/etc/nagios/nagios.d/timing.cfg Adjust the option “max_concurrent_checks” in maximum to the double number of your CPU cores or lower. Per default this value is set to 0 what means start all checks you want