We have 2 custome sensors with powershell. One observing DHCP scopes and another checking the expiary date on certificates. These sensors work well until we change something. If we rename or delete a scope in DHCP, the sensor doesnt get any data anymore (because we identify the channels with the scopename) and sends out an alarm. Only way to get around that, is to delete and recreate the sensor. On the first run, PRTG creates all channels based on the first run and it sticks with them. Is there a solution for this in the future?
I had a look at the API, but it is not possible to create sensors these days. Only workaround is to clone another sensor. But that isnt very beautiful.
Add comment