Correction : Not "ANY conditions" but "ALL conditions" on my alert.

Johann

Le jeu. 16 janv. 2020 à 12:40, Johann Mallet <johann.mallet@zayo.com> a écrit :
Many Thank Mike/Adam!

I have update to r10228.
Update & test my check with ANY conditions :
sensor_value ge @sensor_warn
sensor_warn notnull
I no longer have an error with the null value.
Need testing if alerting working when warm value is triggered.
But I'm very perplexed about detail of entity checked :

image.png

I don't know why value is empty and why test on sensor_limit (notnull) is not displayed.
FYI sensor_limit_warm existing in database :
image.png

Johann

Le jeu. 16 janv. 2020 à 11:15, Klimek, Denis via observium <observium@observium.org> a écrit :

After some time I noticed it’s not :D

All active and positive alerts disappeared. Had to remove the “notnull” condition.

 

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: Mike Stupalov [mailto:mike@stupalov.ru] Im Auftrag von Mike Stupalov
Gesendet: Donnerstag, 16. Januar 2020 10:58
An: Observium; Klimek, Denis via observium
Cc: Klimek, Denis; 'adama@memetic.org'
Betreff: Re: [Observium] Alert : Matching "null" value in condition?

 

Hi,

 really I'm not sure that this should work currently,
because this limits fetched from DB returns as "" (empty string).

:D

I will do additional tests with this conditions,
but I think for this case also possible use:

 sensor_limit ne

(yes, also without last value)

Klimek, Denis via observium wrote on 16.01.2020 11:39:

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




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

 

--
Mike Stupalov
Observium Limited, http://observium.org

_______________________________________________
observium mailing list
observium@observium.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__postman.memetic.org_cgi-2Dbin_mailman_listinfo_observium&d=DwIGaQ&c=JK4-m4bpY8IiuErTs7BTrA&r=B97klcLQm5Jqb6w7uYcb6khPznK64BVW1kslOzg9W04&m=zJf6Au5KTl6Gwe3XtT3K-56cqlG2o4FFGqy-ODMZAm8&s=iXD38JiQykiW3_hP2suU3EeNMOp7WpgJ1GJTyR60qqc&e=