Skip to content
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

Configure logLevel in ClusterFluentBitConfig #1062

Closed
dennis-ge opened this issue Feb 14, 2024 · 0 comments · Fixed by #1063
Closed

Configure logLevel in ClusterFluentBitConfig #1062

dennis-ge opened this issue Feb 14, 2024 · 0 comments · Fixed by #1063
Labels
good first issue Good for newcomers

Comments

@dennis-ge
Copy link
Contributor

Is your feature request related to a problem? Please describe.

In the Helm Chart, when setting Kubernetes to true, the default ClusterFluentBitConfig does not configure the spec.service.logLevel and hence the info log level is applied for the FluentBit pods.

Describe the solution you'd like

I would like to configure the logLevel via the helm chart, e.g., setting it to warning. There is already an option for fluentd in the helm chart: https://github.com/fluent/fluent-operator/blob/master/charts/fluent-operator/values.yaml#L371. I suggest adopting the same approach there, i.e, setting it to "" and then checking in the template:

logLevel: {{ .Values.fluentd.logLevel }}

Additional context

I think this is quite straightforward, I am also happy to provide a PR if this is accepted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants