Skip to content

Optional Redundancy logging to remote S3 location#426

Merged
phutelmyer merged 1 commit into
masterfrom
S3Redundancy
Jan 14, 2024
Merged

Optional Redundancy logging to remote S3 location#426
phutelmyer merged 1 commit into
masterfrom
S3Redundancy

Conversation

@skalupa

@skalupa skalupa commented Jan 12, 2024

Copy link
Copy Markdown
Collaborator

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

  • My code follows the style guidelines of this project
  • I have performed a self-review of and tested my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings

@skalupa skalupa requested a review from phutelmyer January 12, 2024 17:31
@phutelmyer

Copy link
Copy Markdown
Contributor

Thank you @skalupa! Great work and well documented. 👍

@phutelmyer phutelmyer merged commit c127c1c into master Jan 14, 2024
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

Successfully merging this pull request may close these issues.

2 participants