Hi Richard,

I assume this is because sometimes the OIDs from which the limits come aren't polled sometimes?

Is this only a single (os) device? Only a single type of sensor, or multiple? (you should now be able to see the mib/oid on the sensor page)

adam.

On 2019-05-28 10:24:00, Richard Savage via observium <observium@observium.org> wrote:

Hi All

just wonder if anyone has any ideas on this? (Mike / Adam)

Thanks

Richard

On 21/05/2019 14:50, Richard Savage via observium wrote:
Hi All

I have found a bit of a potential bug with the sensor data output which doesnt seem to be related to any particular version of Observium
or device being polled (useful I know!)

However it looks like some sensors limits are being updated to NULL regularly, which is throwing alerts and scaring staff ;-)
Noticed on both 19.3.9774 and 19.4.9840.

e.g from a device event log:

2019-05-10 12:36:07 Ethernet1/49 Lane 2 Transceiver Temperature Sensor updated (limits): limit_high -> "0", limit_high_warn -> "NULL", limit_low -> "0", limit_low_warn -> "NULL"

2019-05-10 13:08:08 Ethernet1/49 Lane 2 Transceiver Transmit Power Dbm Ethernet1/49 Lane 2 Transceiver Transmit Power above threshold: 0.03 dBm (> 0 dBm)




A re-discovery of the affected device will fix the issue, until the next time it happens.

Happy to provide any further debug required.

Thanks

Richard

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