Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consolidate registered alarms data and import existing alarms #13

Open
slominskir opened this issue Feb 23, 2021 · 1 comment
Open

Consolidate registered alarms data and import existing alarms #13

slominskir opened this issue Feb 23, 2021 · 1 comment

Comments

@slominskir
Copy link
Member

Currently we have alarm descriptions stored in two places: the registered alarms topic of Kafka, plus a wiki linked via the docurl field. The wiki duplicates nearly all of the same information and they're currently out-of-sync and alarms are categorized differently. If we add the fields "response/action", "point of contact", and "rationale" to the registered alarms topic we'd have all the same fields. It sounds like we want an admin GUI anyways to make it easy for users to add and manage alarms. For example, configuring the "suppressed by" tree could be done in the admin GUI. At that point, you might as well input the rationale, actions, and point of contact to complete all data. The wiki becomes extraneous and unnecessary, and a searchable viewable web page of alarms could easily be constructed from the kafka data (or admin GUI could probably do that too). Operators client GUI could easily access the data too without popping open a web browser to a Wiki.

@slominskir slominskir changed the title Consolidate registered alarms data Consolidate registered alarms data and import existing alarms Mar 16, 2022
@slominskir
Copy link
Member Author

We originally created a GitHub repo to store alarm definitions here: https://github.com/JeffersonLab/alarms

However, we have recently moved the data into an Oracle database as part of the admin GUI.

Still to consider is if we need some automated sync from the existing alarm system to JAWs to keep it up-to-date or else a manual sync periodically done until the switch over. Further an automated sync from the CED may be useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant