Implement Drain3-based log clustering flow #23
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Please change the PR title to a more meaningful one, it's unclear. |
Superskyyy
added
Algorithm
|
The code to be merged serves the GSOC 2022 task, further enhancements are needed to optimize engine workflow. |
2 tasks
Superskyyy
changed the title
Superskyyy
requested changes
Sep 16, 2022
|
TODO after this PR, add Drain3 License to LICENSE. |
|
Generally looks good to me, thanks! |
Superskyyy
approved these changes
Sep 17, 2022
This was referenced Sep 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The cache for storing log-cluster is added, which saves the process of clustering the same logs repeatedly. Use Redis database to store logs, access logs in the way of streams, and use Ray for Redis stream processing