Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • improve_documentation
  • double_index_any_array
  • configuration_dev
  • 1.0.8 protected
  • 1.0.7 protected
  • 1.0.6 protected
  • 1.0.5 protected
  • 1.0.4 protected
  • 1.0.3 protected
  • 1.0.2 protected
  • 1.0.1 protected
  • 1.0.0 protected
13 results
Blame History Permalink
AlarmEcosystem.md 3.84 KiB

The Alarm Ecosystem

There are several projects related to alarms, which can work together with AlarmHandlers.

AlarmNotify

alarm-notify connect to a list of alarm-handler devices and subscribes for the change event of their alarm attributes. It checks whether there are Recipients configured in individual alarms, or interested in alarms belonging to a group, or all alarms, then builds a list of recipients for each alarm state of each alarm. When an event is received, if there are recipients configured for the new alarm state, a command is triggered on a device for notification. A string parameter with a semicolon-separated list of “key=value” fields is passed to the notification command, with the following keys:

name=<_tag_>;handler=<AlarmHandler device>;values=<JSON attribute values>url=<_url_>;msg=<_msg_>;formula=<_formula_>;groups=<_groups_>;shlvd_time=<_shlvd_time_>;state=<Alarm state DevEnum label>;ack=<true|false>;time=<timestamp>;

See an example of configuration properties:

screenshot

AlarmManager

alarm-manager is a Tango device server that supports the configuration of AlarmHandlers. AlarmHandlers are designed to be modular, so that different AlarmManagers can be configured to handle different groups/subsets of AlarmHandlers. AlarmManager can display the selected alarm configuration as attributes (tag, formula, message, priority, group, shlvd_time, on_delay, off_delay, on_command, off_command, receivers) or can Load/Modify alarms with the configuration provided in the attributes (tag, formula, message, ... same list as above)

AlarmMail

alarm-mail is a Tango device server which exports commands able to send emails. Its commands can be configured in on_command and off_command properties (deprecated) or called by AlarmNotify.

AlarmHandlerGUI

alarm-handler-gui is the default AlarmHandler GUI at Elettra. It is designed to display different sets of AlarmHandlers. See:

screenshot

The different lists of AlarmHandlers to use are taken from free properties. Same properties that can be used to configure AlarmManagers. See:

screenshot

AlarmHandlerGUI is also able to display and search in alarm history stored by HDB++ (MySQL schema only). See:

screenshot

AlarmManagerGUI

alarm-manager-gui displays in a tree the list of alarms read from the AlarmManager's alarmList attribute. When an alarm is selected in the tree, AlarmManager's tag and handler are written accordingly and all the other attributes contain the updated configuration, see:

screenshot

This can then be modified or loaded as a new alarm if the tag attribute has changed.

HDB++

EventSubscriber can be used to store alarm history: alarm are exported by the AlarmHandler interface as DevEnum attributes whose change and archive events are pushed in the code at any variation. The configuration of HDB++ is independent of the AlarmHandlers, but also AlarmManagerGUI can also do this.

PANIC

PANIC is the Alarm System developed at Alba. Preliminary work has been done to support AlarmHandler as an alarm formula evaluation device for PANIC. Specifically, the alarmSummary attribute, GetAlarmInfo command and alarm Devenum attributes are compatible between the two systems. PANIC should also be able of handle the configuation of AlarmHandlers in attribute properties, but the work has not yet been finalized.