I'm sure the alert checker syntax at least used to have the ability to handle nulls.

I have many devices that don't report warning_high and warning_low values, so I would previously write checks that had something along the lines of

sensor_value greater @sensor_limit
@sensor_limit ne null

sensor_value less @sensor_limit_low
@sensor_limit_low ne null

Although that no longer appears to work (null for thresholds) and I'm having to slog through many, many sensors to specify custom thresholds. That's a slight side-issue, but related to your original problem.



You should (hopefully) be able to use 

sensor_value less @sensor_limit_low
sensor_value ne null

But you will need to break the alert checker into two different checks. One for high temps and one for low, as you won't be able to use the "any" condition as it will need to match against all.


Michael




On 10 Jul 2021, at 8:09 am, Joey Stanford via observium <observium@observium.org> wrote:

Hi Adam (et al),

When Obs pulls in a sensor_value of NULL it gets interpreted as a zero and thus triggers alerts.  Can we prevent that somehow?

Joey

Begin forwarded message:

From: "Observium" <observium@rmham.org>
Subject: ALERT: [radio-westcreek.devilshead.rmham] [sensor] [System] Thermal Alarm - Temperature out of threshold
Date: July 9, 2021 at 14:43:53 MDT

ALERTModify
AlertThermal Alarm - Temperature out of threshold
EntitySystem
Conditionssensor_value less -25 ("")
Metricssensor_value = 
Duration5h 43s (2021-07-09 09:43:10)
Device
Deviceradio-westcreek.devilshead.rmham
HardwareRB911-5HacD
Operating SystemMikrotik RouterOS 6.47.10 (Level 3)
LocationDevilsHead, [39.260394,-105.101844]
Uptime7m 28s

sensor_graph

<mLfBrxkBcSHyAa4z.png>

E-mail sent to: netops@rmham.org
E-mail sent at: Fri, 09 Jul 2021 14:43:53 -0600


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