Icinga Powershell Plugins quite heavy on CPU/memory usage

[mattpoel]

trafficstars

We have noticed high CPU usage alerts after adding a couple of smaller Windows application server VMs to the Icinga monitoring using the PowerShell framework/plugins. Upon monitoring the process explorer, we found that the high CPU usage is originating from the PowerShell processes (Icinga PowerShell Plugins) themselves. This is causing CPU bottlenecks when multiple checks are scheduled at the same time:

The execution times of 3-5 seconds for the checks also appear to be quite high. We have observed execution times of up to 15-16 seconds for Invoke-IcingaCheckService on a physical Windows server with almost no CPU usage by non-Icinga processes and a very low CPU usage.

Is this resource usage something to expect?

Cheers!

[mattpoel]

Changing to standard (but deprecated) windows-plugins significantly decreased CPU usage on monitored servers, with checks now executed in the lower ms range.

[tectumopticum]

could you please tell us the versions of the IfW-components you're using (output of 'show-icinga'-command) and the os-versions?

[LordHepipud]

Please have a look on the API check forwarded feature, which will drastically improve performance and resource consumption:

https://icinga.com/docs/icinga-for-windows/latest/doc/110-Installation/30-API-Check-Forwarder/