Hello,
Thank you very much for your feedback. We really appreciate it!
Sensor states is a difficult topic for us though. We already have 14 different sensor states, and we have to ask ourselves, are further states really necessary. Every new state creates a huge follow up in complexity (both in code and for users) as there are a lot of areas where sensor state transitions play important roles (notifications, dependencies, reporting, etc..).
So we have to ask ourselves, how many users would benefit from such a distinct error state here, how much 'man power' would it cost to implement and test, are we risking stability with this (and frankly, with sensor states code, it's the heart of PRTG, so yes it will be a risk), and are there options to achieve this already.
There is an easy way already though to achieve your goal. Simply create a Ticket in PRTG upon the object you want to add the information to. This is exactly intended for informing staff members (with access to PRTG) with tasks related to a certain sensor / device.
best regards.
Add comment