Add custom tail kubernetes tag example #1358
Merged
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.
Adding an example of how to get the
kube.<namespace_name>.<pod_name>.<container_name>.<docker_id>
tag in the Tail Input to actually work.Also, fixing the regex in the Tail documentation to reflect how it worked for me.
Now that I begin to understand what is actually happening, I realize you don't need the above notation to split by namespace, pod, container, or Docker ID. However, for me, the above tag feels more intuitive. From my online research, many people have struggled with this, and there are blog posts that arguably do it worse (no disrespect, these two articles are still helpful):
https://blog.omerh.me/post/2020/05/splitting-kubernetes-logs-by-namespaces-with-fluentbit/
This could work (though it did not for me):
https://www.agilicus.com/routing-to-multiple-outputs-by-kubernetes-namespace-in-fluent-bit/