I am aware of several discussions about CPU load caused by Icinga PowerShell Plugins (Invoke-IcingaCheck…), but still I am wondering how everybody out ther is dealing with the current situation.
I know about three main options to check on Windows:
- Windows Plugins for Icinga 2 - these are deprecated
- NSClient++ - the latest stable release is 3 years ago
- Icinga PowerShell Plugins - currently have severe load impact on smaller machines
Looking closer at the load aspect, we did some measuring on a 1-core, 2 GB RAM Windows VM and found (in a steady state with default settings, checking load, memory, and disks):
- no significant overhead with Windows plugins for Icinga 2
- less than 1% additional CPU load with NSClient++ (nscp-local)
- ca. 15% additional CPU load with Icinga PowerShell Plugins (v1.6.0 - earlier versions created significantly more load)
Having this, option 3. is a no-go for us especially on smaller webservers.
As 1. is deprecated and 2. is not maintained for a longer timeframe, how do you deal with this situation in your (large) Windows environment?
Did we miss something in our project? I am eager to read about your opinion & experience!