Hi all,

Thank you for adding this option J We also had some false positives due this missing function.

I changed some alerts now and it’s working fine so far.

Example test condition (require all conditions):

sensor_value ge @sensor_limit

sensor_value ne 0

sensor_limit notnull

Mit freundlichem Gruß

Stadtwerke Norderstedt

Denis Klimek

Carrier Manager & Professional Network Engineer

IP-Systemtechnik

Tel: +49 (0) 40 / 521 04 – 1049

dklimek@stadtwerke-norderstedt.de

www.stadtwerke-norderstedt.de

Von: observium [mailto:observium-bounces@observium.org] Im Auftrag von Adam Armstrong via observium
Gesendet: Mittwoch, 15. Januar 2020 22:08
An: 'Observium'
Cc: adama@memetic.org
Betreff: Re: [Observium] Alert : Matching "null" value in condition?

Does  “sensor_value notmatch“ work?

That’ll end up being  ‘ if $sensor_value != “” ‘ or there abouts

I’ve just added “isnull” and “notnull” operators (last argument isn’t used), but you need to be running r10226 for that.

Adam.

From: observium <observium-bounces@observium.org> On Behalf Of Johann Mallet via observium
Sent: 15 January 2020 17:38
To: Observium Network Observation System <observium@observium.org>
Cc: Johann Mallet <johann.mallet@zayo.com>
Subject: [Observium] Alert : Matching "null" value in condition?

Hello,

In alerting, do you have the option to match "null" value?

For example, to match/not match the sensor with sensor_limit_warm = null value.

My goal it's create alerting with "sensor_value gt @sensor_warn" but excluding when sensor_warm is "null" in database. Because that's create false positives.

Thanks!

Johann