Would it be possible to query alarms from haystack ?
I know it's not an equipment, but it could be something useful for an analyser tool to track alarm database to know wich are recurring, happening when, etc.
Brian FrankSun 24 Jun 2012
I guess we could add that if the community wants to see it go there. But if you get into alarms, then that starts to duplicate the sophistication and complexity of oBIX - not sure we really want to go there right now.
Christian TremblaySat 7 Jul 2012
I've thought about that and came to the idea that an alarm is in fact "linked" to a point we already tagged (documented) in haystack. So alarms are in fact a tag to a point. What we could think about would be a relational kind of link between a point tagged and the alarm linked to this point.
Technically, we have access to 1 database of tagged points and 1 database containing alarms. We should not need to tag/document the alarms as we already documented the points. But if we can make a kind of pivot relation between the 2 databases we are then able to add a lot of information to our request.
In most of system (I guess) the relation already exist : alarm source.
The link could then be made automatically by the haystack module.
Once the relation exists, if alarm info is passed as string value, analyzer will be able to extract what he is looking for.
Christian Tremblay Thu 21 Jun 2012
Would it be possible to query alarms from haystack ?
I know it's not an equipment, but it could be something useful for an analyser tool to track alarm database to know wich are recurring, happening when, etc.
Brian Frank Sun 24 Jun 2012
I guess we could add that if the community wants to see it go there. But if you get into alarms, then that starts to duplicate the sophistication and complexity of oBIX - not sure we really want to go there right now.
Christian Tremblay Sat 7 Jul 2012
I've thought about that and came to the idea that an alarm is in fact "linked" to a point we already tagged (documented) in haystack. So alarms are in fact a tag to a point. What we could think about would be a relational kind of link between a point tagged and the alarm linked to this point.
Technically, we have access to 1 database of tagged points and 1 database containing alarms. We should not need to tag/document the alarms as we already documented the points. But if we can make a kind of pivot relation between the 2 databases we are then able to add a lot of information to our request.
In most of system (I guess) the relation already exist : alarm source.
The link could then be made automatically by the haystack module.
Once the relation exists, if alarm info is passed as string value, analyzer will be able to extract what he is looking for.