Support the Standalone Alarm Logging service #3186
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Kunal @shroffk and Kay @kasemir
Based on our mode of operation, we want to run the alarm logging service (alarm-logger) as a standalone service.
For the elasticsearch folder relocation with the limited requirement, we've verified that the Pheobus alarm log table and the standalone alarm logging service work well without printing our so many error messages regarding the communication to the alarm server (Kafka). This could be a potential use for independent alarm studies without interfering with a production environment.
Please let us know what you think about this PR.
@jeonghanlee, Soo Ryu, and @Sangil-Lee at ALS-U Controls, LBNL.
P.S. I @jeonghanlee updated the README to reflect the minimal documentation description of the service. It looks like a lot of the documentation will be updated to reflect what we have changed since a couple of years ago. We can discuss them when we have the meeting together later this year or next year.