Ahh I understand. Already did that for several sensors but not for all because I dont know their real low/high limit values.
For some sensors I read the manual of the device or checked their limits through CLI. Anyway, thanks for the confirmation that someone
else is using this „custom_limit“ option to supress the eventlogs.
I will think about it using it for other sensors too.
J
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
Von: Torstein Eide <torsteine@gmail.com>
Gesendet: Montag, 2. März 2020 09:47
An: Klimek, Denis <DKlimek@Stadtwerke-Norderstedt.de>
Cc: Observium <observium@observium.org>
Betreff: Re: [Observium] Supress Sensor Updated in Eventlog
In mysql i have used the following commands to change the sensors for volt to "custom limits";
To show status:
#SELECT `sensor_id`,`sensor_custom_limit` , `sensor_descr`, `sensor_value` , `sensor_limit`, `sensor_class` FROM `sensors` where `sensor_class` like '%volt%' AND `sensor_value` BETWEEN '200' AND '250' ;
To change to sensor_custom_limit to True:
# UPDATE `status` SET `sensor_custom_limit` = '1' WHERE `sensor_class` like '%volt%' ;
other commands i have used:
#UPDATE `sensors` SET `sensor_limit` = '12.6' where `sensor_class` like '%volt%' AND `sensor_value` BETWEEN '10' AND '15' ;
#UPDATE `sensors` SET `sensor_limit_low` = '11.4' where `sensor_class` like '%volt%' AND `sensor_value` BETWEEN '10' AND '15' ;
#UPDATE `sensors` SET `sensor_limit` = '440' where `sensor_class` like '%volt%' AND `sensor_value` BETWEEN '380' AND '440' ;
#UPDATE `sensors` SET `sensor_limit_low` = '380' where `sensor_class` like '%volt%' AND `sensor_value` BETWEEN '380' AND '440' ;
#UPDATE `sensors` SET `sensor_limit` = '5.25' where `sensor_class` like '%volt%' AND `sensor_value` BETWEEN '4' AND '6' ;
#UPDATE `sensors` SET `sensor_limit_low` = '4.75' where `sensor_class` like '%volt%' AND `sensor_value` BETWEEN '4' AND '6' ;
tor. 27. feb. 2020 kl. 14:47 skrev Klimek, Denis <DKlimek@stadtwerke-norderstedt.de>:
Hi Torstein,
I really do not know what you mean with „user defined database“. Can you explain a little bit more?
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
Von: Torstein Eide <torsteine@gmail.com>
Gesendet: Mittwoch, 26. Februar 2020 17:53
An: Observium <observium@observium.org>
Cc: Klimek, Denis <DKlimek@Stadtwerke-Norderstedt.de>
Betreff: Re: [Observium] Supress Sensor Updated in Eventlog
I found it easyes to change in datebase to user defined, since there is no UI to mass edit.
I think Adam talk about adding to the API, but I have ot tested that.
ons. 26. feb. 2020, 15:39 skrev Klimek, Denis via observium <observium@observium.org>:
Hi all,
is there any method to supress the generation of „Sensor updated“-Eventlog entries if Observium is dynamicly changing the limit_low/high value?
Our eventlog contains shitloads of entries for this kind of logs and they are not really useful from my opinion. So we would like to keep the sensors quiet.Currently we are running an external scripts triggered by cronjob to filter out those messages, but if we would supress the creation itself it would be much better
Cheers,
Denis
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
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
--
Torstein Eide
Torsteine@gmail.com