Alarm apps

[shroffk]

Make the alarm logging and the alarm config logging services more resilient by making them poll for missing topics

If topics are deleted/removed/go missing then the services start throwing exceptions

Checklist

• Testing:

  • The feature has automated tests
  • Tests were run
  • If not, explain how you tested your changes

• Documentation:

  • The feature is documented
  • The documentation is up to date
  • Release notes:
    • Added an entry if the change is breaking or significant
    • Added an entry when adding a new feature

[lcaouen]

tested with kafka 2.13

using master branch

• start alarm server and alarm_logger services => I see alarms in Phoebus
• delete topics => no more alarm
• restart alarm_logger => get alarms so we need to restart the service with old version

using alarm branch (https://github.com/ControlSystemStudio/phoebus/tree/alarm_apps)

• using new alarm_logger => start it, alarms are displayed
• delete topics => no more alarm
• restart alarm_logger => alarm logger subscribe again to kafka and get the alarm
• however no message saying it's reconnecting successfully (see attachment)

out.txt

[sonarqubecloud]

Quality Gate failed

Failed conditions
82.4% Duplication on New Code (required ≤ 3%)
B Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[lcaouen]

out.txt
New logs.
No more extra rest.SearchLogger logs

[lcaouen]

Alarm logger subscribes automatically to kafka after deleting and recreating the topics.
Less unnecessary logs