Haha, that's pretty annoying.

The discovery code can change the precision, and by the looks of it, that's what's happening.

I can't say for sure, but it's likely that discovery module is getting the precision from the device. You can see what's happening by running the sensor discovery module in debug mode :

./discovery.php -h <host> -m sensors -d

adam.

On 28/01/2016 22:43:30, Michael <observium@smarsz.com> wrote:
Has anybody encountered devices that change their scale/precision whenever they feel like it?

We have some that now behave this way after a recent software upgrade. We think it's a vendor bug (in this instance, Bluecoat), but might be prudent to catch the changing precision value during the poll.

Currently it looks like the precision is detected once and stored in the db. Then subsequent polling is only adjusted based on the original precision value.

I've attached a graph and some walks showing the behaviour...

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium