Looking for information if possible please. With 3alarm servers, 1alarm logger configured with kafka, zookeeper and elastic search, I would like to know how the alarm config logger manages the git repository.
With a single alarm server the alarm config logger records the alarm evolution followed as expected - branch master (not Accelerator as configured in the alarm server). However, having arranged an additional two alarm servers, I have just noticed that the git repo looks to be blank apart from the top level config.xml. I was wondering whether new branches are to appear for each configured alarm-server, although only master is currently present.
Actually, is it one alarm-config-logger per alarm-server i.e. per "alarm_topics". I made the assumption that the alarms_topics was a comma separated list.
Looking for information if possible please. With 3alarm servers, 1alarm logger configured with kafka, zookeeper and elastic search, I would like to know how the alarm config logger manages the git repository.
With a single alarm server the alarm config logger records the alarm evolution followed as expected - branch master (not Accelerator as configured in the alarm server). However, having arranged an additional two alarm servers, I have just noticed that the git repo looks to be blank apart from the top level config.xml. I was wondering whether new branches are to appear for each configured alarm-server, although only master is currently present.
Note : we are using Docker to run these services.