Alarm Automated Action to create an electronic logbook entry

[utzeln]

It is required for ITER to register in the electronic logbook (Olog) safety and interlock events as well as “important” alarms.

One solution could be to have an alarm configuration specific for these operation events that trigger an automatic action such as “create a new entry” using Olog Java Client API (http://olog.github.io/2.2.4-SNAPSHOT/modules/OlogAPI/).

We should also be able to reuse some code from the current interface between the Alarm Tree/Table and the logbook.

Have you similar concerns or requirements that we need to take into account?

[kasemir]

We have several tools that monitor various things and make logbook entries.
Most of them run once a day to log summaries, like

• Number of beam trips and their sources
• Downtime statistics
• Beam power statistics for the day
  For that, it's good to have a (scripting) language where you can generate the report, with interfaces to the live data (like python with a channel access client) and to the logbook (like the OLog with a web service interface). Since each such script is quite a specific tool, I don't think it's useful the generalize it.

You already mention a separate alarm configuration for your operation events. They could already trigger automated actions which call an external command. If your external command is a python script, it could already generate a nice looking report and submit it to the OLog via its web interface.

[utzeln]

The automated action configured for an alarm PV to create automatically an entry in the logbook is more or less complete.

The provided Help is:

Electronic Logbook Notifications

Electronic Logbook notifications start with "log:" and require the
specification of at least one logbook. It will create a new entry with alarm
information such as:
/demo/TEST-BST0/TEST-BST0:
MAJOR alarm: Whenever the LOW switch becomes dry, the pump will be forced OFF
PV : TEST-BST0:LOW-SWITCH
Alarm Time : 2014/04/09 13:35:610 (Time since event: 0:01:01)
Alarm Severity/Message : MAJOR/STATE_ALARM
Alarm Value : Dry
Current Severity/Message: MAJOR/STATE_ALARM

Examples:

log:Sandbox
log:Cryo, Maintenance&level=Problem&tags=session_leader
log:Cryo&body={0} Alarm raised - Water below {1} m3
Within the configuration, the text {0} will be replaced with the alarm severity
and {1} with the value that triggered the alarm.

[kasemir]

I'm sorry, I missed the "OLog". I thought this would be a generic make-logbook-entry action, based on the CSS logbook API, usable with the SNS logbook, the OLog, the recently supported GANIL logbook #143, others.

Would it be possible to change org.csstudio.alarm.beast.notifier.olog into a generic org.csstudio.alarm.beast.notifier.logbook plugin that works for any logbook? What do you need that is currently only available in edu.msu.nscl.olog.api and not org.csstudio.logbook?

[arnaudf-iter]

Yes, it is possible.
In fact, edu.msu.nscl.olog.api is a useless dependency for this plugin... (only used in our site-specific fragment).

[kasemir]

Excellent!
This makes it a little harder to build the notifier, since we'd have to build

• plain notifier (email, commands)
• notifier with added logbook support for OLog
• notifier with added logbook support for SNS logbook
• notifier with added logbook support for GANIL logbook

So the notifier turns into a product similar to the CSS main GUI, it becomes site-specific. But once we figure out how to do that for the main GUI, it'll be easy to replicate for the smaller notifier ;-)

[berryma4]

Could each be different features?

On Wed, Apr 23, 2014 at 11:18 AM, kasemir notifications@github.com wrote:

Excellent!
This makes it a little harder to build the notifier, since we'd have to
build

• plain notifier (email, commands)
• notifier with added logbook support for OLog
• notifier with added logbook support for SNS logbook
• notifier with added logbook support for GANIL logbook

So the notifier turns into a product similar to the CSS main GUI, it
becomes site-specific. But once we figure out how to do that for the main
GUI, it'll be easy to replicate for the smaller notifier ;-)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/354#issuecomment-41173855
.

[kasemir]

Thanks for making it more generic, and also for the log messages with 'Exception' (thus stack trace) instead of 'Exception.getMessage()'