We have our system separated with multiple remote probes and a local probe (Web Server). The local probes stay around 50 threads but our remote probe that does the bulk of our checking is running in the low 500s. Is this an issue means it's not the webserver? If it is an issue how do I lower the number because I tried pausing checks and the number didn't lower. The remote probe is running on Windows Server 2012.
Threads on remote probe
Modified on 2025-06-10 14:13:27 +0200
Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
Hello,
thank you very much for your KB-Post. The threads of a Probe are not related to the Webserver (that's the PRTG Core), but are scan-threads. So Threads that basically "talk" to your devices. Please do not limit the number their. A Probe is limited to 500 scan threads (plus a few organizational threads), is this number is limited, it will have a dramatic impact on the monitoring. Because then monitoring requests can only be sent in a serial manner, which will make scanning intervals much much longer.
best regards.
Jul, 2013 - Permalink