Mutualize Powershell for custom sensors

Hello dgiraud,
thank you for your post.

I'll answer your questions in reverse because I want to start with the last one:

3. "There are naive questions, tedious questions, ill-phrased questions, questions put after inadequate self-criticism. But every question is a cry to understand the world. There is no such thing as a (silly) question". -Carl Sagan

2. There are actually a couple of approaches to this, I will list some of them that should apply in your case:

• Run the script as one (or multiple) windows task(s) and write all results to disk on the probe, then use a small(er) Powershell EXE/Script Advanced Sensor to simply "read" the XML file(which will be very fast), similar to what is explained here. For multiple scripts, save the outputs as "sensor_123456.txt" (or device_123456) and then either supply %sensorid or %deviceid as a parameter to the sensor that reads the file from disk.
• Run the scripts either on the PRTG Probe or on the Monitored Device(s) and write the XML result somewhere where it can be read with the HTTP Data Advanced Sensor. This is a very advisable approach because it completely removes the overhead for custom Exe/Script sensors.
• Run the scripts as windows tasks directly on the "monitored device" and PUSH the results into PRTG using HTTP with the HTTP Push Data Advanced Sensor as described here.

1. Due to the way that the scheduler (which balances monitoring requests) within the PRTG Probe works this is not something that would be easily implemented and as there are several alternatives something that we're not considering at the moment.

Best Regards,

Thank you so much for your exhaustive answer
Some explanations about my question and why I can neither use HTTP Data Advanced sensor or run the script from the device
It is a custom application and we agreed on a protocol (kind of telnet based) with the developer because they are specialized devices we cannot touch The result yields several fields (Status and client version) wich I parse in PS to provide PRTG an error code and a message:
"Active - Version client 2.3.7.19339"

I had in mind to report all installed versions in the future to simplify update planning (this is another topic and I'll check the API before asking here how to) I found it simpler to make a PS script while keeping in mind that I may have got to make a small exe which is quite simple (only read a socket and parse an xml)

About point 3: Thank you for the nice quote