Be able to install a probe on Windows to replace the WMI sensors
With the high performance costs (to the PRTG hosting systems) of WMI sensors, since they are not availability (ping/port/url), have a Windows probe which would shift the WMI sensors to be local sensors to the windows host and then publish the metrics/state to the PRTG hosting systems. So this would shift the WMI sensors from a pull from the PRTG host, to a publish from a PRTG probe model.
With this, the operational costs of the WMI are shifted to the target instead of at the PRTG hosting server side.
Hi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
Thank you for the idea, but due to the core limitations of 30-80 probes per core (based on installation specific sizing) this would not be a scalable solution. We are not planning to deliver an agent based solution anytime soon.
After careful consideration by our team, we've decided to decline this idea at this time.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
billy.cole@pheaa.org
commented
With the remote probe installation on a windows server, the base probe device has a number of metrics such as disk space which is published to the core/cluster probe. The disk space sensor, if it was able to be separated out to separate drives so that a notification threshold-trigger could be set to a specific drive, would save on having to configure a WMI sensor from the core/cluster to the target window server, and if in a cluster, both the core and failover both would have WMI connections.
Similarly, with the WMI Service sensor, if the remote probe could also pull state from the hosting server, the core/cluster nodes wouldn't need to use the WMI Services sensor.