Advanced EXE/Script Sensor: Allow the script to change limits dynamically after sensor creation

Want this feature implemented, too? Please upvote by clicking Thumbs up!

(Posts as a reply won't be published in this feature request thread. Read Me!)

User story

As a PRTG user / developer, I want the Advanced EXE/Script Sensor to be able to handle changed limit values over the time.

Details of user story

Custom sensors can perform several monitoring tasks that extend the standard sensor set and provide a great flexibility. Right now, once they are set up, including their limits, limits can't be changed directly by the developed sensor. Instead, it is required to make that change calling the PRTG API, making it unnecessarily complex to change those values. https://www.paessler.com/manuals/prtg/custom_sensors

Acceptance criteria

• PRTG changes limit values, according to the values in the json/xml, files after that the sensor and channels are created.

Status

Open

custom-sensors dynamic-limits improve-prtg prtg-kbtracker