Details
Minor Description
There are sensor alerts for the Tx and Power values for disabled interfaces.
Of course the interface is not using any power and not sending light.... but it's disabled that's a correct behavior 
Maybe you can fix that.
Attached a screenshot.
Attachments
Activity
Pls see latest changes in r9759.
On sensors/status page added form with ability filter by measured status (none/up/down/shutdown).
i also think it would be better to skip interface sensors of a disabled interface. If they are shown at the dashboard it will never get silent, and you have to look in depth to see if it is a real problem.
Hi Mike,
that looks good for custom alerts and makes sense. But the origin issue is still present.
I mean the alerts that are generelly generated at ../health/metric=sensors/event=alert%2Cwarning/
This site shows i.e. alerts for transceivers with -40dBm but the interface is disabled on the device.
Of course the transceiver is not transmitting any light if the interface is disabled and is also not consuming any power/ampere for the TX laser.
Ok, in r9740 I added ability for select sensor/status entities by measured entities.
For your case I promote this way:
- Create new (or use any self) group with all disabled/down ports.
- Add into "Sensor Measured Port Droup" this created group as [not in].
See example:
I noticed that the status value of entSensorStatus.index is not getting used for setting the sensor status in some cases. Attached is a screenshot and I also sent you a debug log for the sensors. In Logs you can see that the device it displays "ok", but Observium is giving an alert state for the sensor.