You should probably show some screenshots of what’s going on (don’t attach them to the email though, they’ll likely be too big).
It’s very unlikely that Observium would remove something that it had already added, since that’d require the code to be able to behave differently given identical input.
The only thing likely to cause anything to be removed from the alerting tables is the underlying entity itself being removed, but I assume you already checked for this. The method of adding things to the alerting table is just a SQL statement built from the associations rules, so it’s not really easy for things to be added and then removed, without something being changed.
Adam.
From: Tibi, Saleh <Tibi.Saleh@uni-duesseldorf.de>
Sent: 04 November 2020 06:47
To: Adam Armstrong <adama@observium.org>; Rando Sui via observium <observium@observium.org>
Subject: Re: question and a problem in Check alert
Hi,
Our alerting system as it exists isn't capable of doing this by itself, though you could write your own status entry to do it, it's sort of fiddly.
can u pls give me a hint how and where i can start. Is there any good documented example or something like this. i am new to Observium. and i need to do this.
one more thing i thought. it will be easier if i could inject an external test condition throw a file, is this possible ? or easy :D ..
By disappearing, it's likely they're now "ok", and your alert table filters are for non-ok only?
Look at the right hand side of the table header.
NO.
before disappearing (at the right hand side of the table header) the greyed number will give 22 that the number of my Sensors. and after about 3 minutes all colored number will be 0. and the table will be empty. sometimes it mange to change the status of one or two sensors to OK. still those Sensors with Ok Status will disappear with the Unkown Status Sensors.
Notice: our Observium is updated instance and not Fresh install one. i have an old Check-alert with the same senors which we created before (with old method of filtering with old version of Observium)when the filtering was design to take only two filed Device Association & Entity Association.
thx in advanced
Saleh
From: Adam Armstrong <adama@observium.org>
Sent: Tuesday, November 3, 2020 4:55 PM
To: Rando Sui via observium
Cc: Tibi, Saleh
Subject: Re: [Observium] WG: question and a problem in Check alert
Hi,
Our alerting system as it exists isn't capable of doing this by itself, though you could write your own status entry to do it, it's sort of fiddly.
When you first configure an alert checkers everything will be unknown because they won't have been yet checked by the alert system.
By disappearing, it's likely they're now "ok", and your alert table filters are for non-ok only?
Look at the right hand side of the table header.
Not at a computer at the moment so I can't check :)
Adam.
Sent from BlueMail
On 3 Nov 2020, at 14:45, "Tibi, Saleh via observium" <observium@observium.org> wrote:
Hi guys,
our instance: observium 20.10.10799(rolling)
i have two issues (a question and a problem ) in the subject Alert Checkers.
The question:
Is it Possible to configure my alert Checkers that test two different sensors (different entities ) I have two sensor
- flowrate Sensor
- Valve Sensor
For example like this:
Require all conditions:
(flowrate Sensor)sensor_value eq 0
(Valve Sensor)sensor_value eq 0
What I saw in the documentation that we can check only one entity at a time.
The Problem:
Steps:
1- Creating new alert Checker
2- filtering devices or sensors in Entity Association Ruleset (for example: Sensor Group in WaterSensor)
3- save changes (all sensor will be listed )
4- rebuild
5- all sensor appearing in status unknown
6- wait a 3 or 4 minutes all sensors will disappear
any advices or hint ?
thx in advanced an have a nice Day
Saleh Tibi
Mit freundlichen Grüßen
Saleh Tibi
----------------------------------------------
Ing: Saleh Tibi (Herr)
IT-Spezialist für Maschinensäle und Überwachung
Zentrum für Informations- und Medientechnologie (ZIM)|Raum 25.41.02.27
Heinrich-Heine-Universitaet Duesseldorf
Universitaetsstrasse 1
40225 Duesseldorf
Email: Tibi.saleh@uni-duesseldorf.de
Phone: +49-(0)211-81-14051
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium