Good morning,
I monitor the IIS (Template Microsoft IIS).
We have 85 IIS sites and AppPools on the server.
Unfortunately, that pretty much affects performance.
In the task manager I keep seeing the powershells coming up (about 3-6 seconds)
"powershell -NoProfile -ExecutionPolicy Bypass -File C:\sys_batch\zabbix\iis\get_sitestate.ps1 "website_1""
etc., just for each AppPool.
If I give the command
"powershell -NoProfile -ExecutionPolicy Bypass -File C:\sys_batch\zabbix\iis\get_sitestate.ps1 "website_1""
So directly in a CMD (as admin), is it much faster and also uses significantly less CPU?
The checks run every 5 minutes and then drain up to 90% CPU for about 2 minutes.
Can I somehow lower the priority of the command/check, or tell it to only use 20% of the CPU?
Is there a good approach?
It wouldn't bother me if the check ran a total of one minute longer and used a little less CPU.
If I output all states in one (1) Powershell session, this does not consume any CPU. I suspect the problem is launching a powershell session for each request. If a powershell script that uses the Zabbix would be open all the time, it would be worlds more performant.
Zabbix 5.0.26
Thanks!
I monitor the IIS (Template Microsoft IIS).
We have 85 IIS sites and AppPools on the server.
Unfortunately, that pretty much affects performance.
In the task manager I keep seeing the powershells coming up (about 3-6 seconds)
"powershell -NoProfile -ExecutionPolicy Bypass -File C:\sys_batch\zabbix\iis\get_sitestate.ps1 "website_1""
etc., just for each AppPool.
If I give the command
"powershell -NoProfile -ExecutionPolicy Bypass -File C:\sys_batch\zabbix\iis\get_sitestate.ps1 "website_1""
So directly in a CMD (as admin), is it much faster and also uses significantly less CPU?
The checks run every 5 minutes and then drain up to 90% CPU for about 2 minutes.
Can I somehow lower the priority of the command/check, or tell it to only use 20% of the CPU?
Is there a good approach?
It wouldn't bother me if the check ran a total of one minute longer and used a little less CPU.
If I output all states in one (1) Powershell session, this does not consume any CPU. I suspect the problem is launching a powershell session for each request. If a powershell script that uses the Zabbix would be open all the time, it would be worlds more performant.
Zabbix 5.0.26
Thanks!