I'm creating a sensor that is not meant to return an explicit result on every run, and the state of the sensor should stay the same as before unless a different result is returned explicitly. I take it from the PRTG manual that this is exactly what the state "None" in value lookups is for, as the manual says: '"None" will not trigger a status change'. However, a status change is triggered nonetheless when the sensor switches from 'Error' to 'None': The channel meter shows state 'None', the corresponding channel show state 'None', but the head bar of the sensor turns green and says "OK". What to do to have the 'None' state not change the sensors status when being returned?
Value lookup state "None" triggers status change
Votes:
0
1 Reply
Votes:
0
Dear Ages,
If the lookup state is not error or warning and if there are no limits or other errors the sensor state will be shown as up. This is why if you set the lookup state=none, the sensor will be up. At the moment there is no possibility to ignore the status of the sensor result. The sensor state None cannot be generated by a sensor result.
The status change appears in your scenario as the sensor switches from a warning / error lookup to a none lookup, which is an "okay" state as there is no error.
Best regards
Created on Dec 4, 2014 8:11:58 AM by
Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
Add comment