-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fluentbit loading unwanted index patterns #27
Comments
Good catch @dfishburn Can pls you create e PR against the main branch in this repo? I will merge it. Thanks |
@nickytd the PR is at the top of the issue, did I do it correctly? |
The correct handling of the The Here is a pattern that demonstrates how to redirect the logs from a specific workload to its own index in fluent-bit configuration
Follow the naming convention for the files using the |
@nickytd the changes you checked in did not include these changes:
And the same for systemd. |
2 issues with
kubernetes-logging-helm/chart/templates/fluent-bit/fluent-bit-config-sec.yaml
.First issue:
Only tests if the variable exists, not whether it is true or false.
This was showing up when I ran:
You will see the
@INCLUDE _output-kafka.conf
, even though I had defined:Updating the
if
to validate the variable is set totrue
resolves this.2nd issue
The default indexPatterns is set to:
In my case, the containers where chewing up all available space on my system.
I had already created a custom setup so that my logs were indexed under a separate pattern.
Therefore, I was not interested in the
containers
at all.Removed
- containers
, unfortunately, the OUTPUT is still created and logged.This change will prevent the creation of the
[OUTPUT]
if the deployment has not requested that index.It was put into the file using this syntax:
I had originally set it up as:
But later on in this file we were issuing:
And if we had so happened to turn off BOTH the
systemd
andcontainers
then this line would fail as there would be no files which would meet the wildcard.Leaving it as I have has worked for me.
The text was updated successfully, but these errors were encountered: