●1 KNOWLEDGE BASE. Presumably you’ve got some specific purpose intended for your custom sensor – possibly some esoteric metric that some gizmo on your network is capable of reporting, but it does so by some arbitrary, partially-formatted method. PRTG then tries to discover the stored sensors on the device. (62) And that’s it: you’ve got a custom sensor. It is beta, does not support smart URL lookups (sensor only reports locally). Select either the EXE/Script sensor or the EXE/Script (Advanced) sensor. Minimum PowerShell version. In upcoming post, I'll explain how to use the prtgshell PowerShell Module together with VMware / NetApp/ Active Directory/Citrix etc. ●1. powershell Channels are the thing that contain actual monitoring values. This option is provided as part of the PRTG API. share. PRTG Manual: EXE/Script Sensor. Downloaded scripts have to be signed prior to execution. Out-of-the-box, PRTG supports a pretty wide gamut of sensors and should be able to give you reasonably comprehensive monitoring of most network devices. hide. You’ve possibly already added this device to PRTG, and maybe even have some other sensors configured for it – ping, SNMP traffic, etc. There are a few settings that you cannot save into a device template, so PRTG sets them to default, for example: The EXE/Script Advanced sensor type expects the data to be returned in an XML format. But there is a custom sensor that will run a PowerShell script.