Evaluate different log aggregation/streaming approaches #91
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
hopefully still no log collection recursion.
actually getting amazingly close to the result from filebeat or fluentd. The `==> [filename] <==` messages give the filename for coming nessages up to the next such line (thanks to `tail`) and the filenames all have the pattern pod-name_namespace_container-name_id.log A streams application could process this and pass messages to another topic, after adding labels and annotations from kube API, either as very long keys or wrapping as json like fluentd or filebeat does.
although it will never be reliable in clusters with a lot of scheduling going on
taking into account that pod's own log file might not be there at start. Now I actually get 1 logs-kafka-raw per 1 container deletion.
(I know you're close)
and though it looked like unhealthy nodes I see no reason for a longer grace period with neither tail nor kafkacat.
Addresses #88 (comment). I deemed it safe to assume that operational daemonset pods never co-exist on a node. Tests edenhill/kcat#123, as does 53f355a.
solsson
changed the title
|
And the winner is ... #131 :) |
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.
Experimenting with different ways to aggregate logs, here and in #88. Supersedes #40.