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.demailto:dklimek@stadtwerke-norderstedt.de www.stadtwerke-norderstedt.dehttp://www.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.orgmailto: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.demailto:dklimek@stadtwerke-norderstedt.de www.stadtwerke-norderstedt.dehttp://www.stadtwerke-norderstedt.de/
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium