Describe the change
In the case of an interruption to the Kafka Producer connection to the corresponding broker topic, this PR adds in the option to toggle on a redundancy system such that logs for the past three hours are sent to a remote S3 location so that no data is lost during the Kafka interruption. Once connection to the Kafka broker resumes, either by self-healing or by restarting the frontend, the redundancy logs will be pulled from the remote S3 location and sent in parallel with incoming processed logs.
This feature is dependent on the Kafka Producer option being set to true in the Dockerfile, and, due to this fact, defaults to false in normal running of the application.
Describe testing procedures
Code has been tested with a local instance of the Strelka containers.
Sample output
N/A
Checklist
[X] My code follows the style guidelines of this project
[X] I have performed a self-review of and tested my code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
Describe the change In the case of an interruption to the Kafka Producer connection to the corresponding broker topic, this PR adds in the option to toggle on a redundancy system such that logs for the past three hours are sent to a remote S3 location so that no data is lost during the Kafka interruption. Once connection to the Kafka broker resumes, either by self-healing or by restarting the frontend, the redundancy logs will be pulled from the remote S3 location and sent in parallel with incoming processed logs.
This feature is dependent on the Kafka Producer option being set to true in the Dockerfile, and, due to this fact, defaults to false in normal running of the application.
Describe testing procedures Code has been tested with a local instance of the Strelka containers.
Sample output N/A
Checklist