You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
Changing to standard (but deprecated) windows-plugins significantly decreased CPU usage on monitored servers, with checks now executed in the lower ms range.
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!
The text was updated successfully, but these errors were encountered: