Collect logs with FluentBit and Fluentd #34
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.
The goal of this PR is to create a FluentBit daemonset that collects the same logs as the existing Fluentd setup here.
The FluentBit daemonset will send the logs (without any preprocessing to keep it lightweight) to the Fluentd deployment, which acts as an aggregator, attaches the relevant metadata to the logs, then forwards to Sumo.
We make no code changes in this PR - we utilize the FluentBit helm chart to make only config changes. The filter plugin from
fluentd-kubernetes-sumologic
is copied over as isSteps for installing (will update the README's in a future PR):
FYI - @maimaisie @yuting-liu @rvmiller89