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

FluentbitAgent: configuring filterKubernete.K8S-Logging.Parser should enable inputTail.multiline.parser #1956

Open
baby-gnu opened this issue Feb 26, 2025 · 2 comments

Comments

@baby-gnu
Copy link

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

It took times to have a working setup with kubernetes pod annotation.

Describe the solution you'd like

When filterKubernete.K8S-Logging.Parser is enabled, the inputTail.multiline.parser is automatically enabled too.

Describe alternatives you've considered

Add a note in documentation explicitly describing the mandatory dependency.

Additional context

I initially opened an issue is fluent-bit and finally found the solution: I had to manually configure inputTail.multiline.parser

Thanks.

@pepov
Copy link
Member

pepov commented Mar 4, 2025

@baby-gnu thanks for the report! Can you add your working configuration snippet here as the example we should provide?

@baby-gnu
Copy link
Author

baby-gnu commented Mar 4, 2025

Hello

Here is my working configuration:

  • inputTail.multiline.parser: make filterKubernetes.K8S-Logging.Parser: "On" really works
  • Merge_Log_Key: "parsed": is optional but adding keys at top level is risky because it can result in conflicting keys (for example the host from k8s-nginx-ingress conflicting with the kubernetes host)
---
apiVersion: logging.banzaicloud.io/v1beta1
kind: FluentbitAgent
metadata:
  name: example-fluentbit
spec:
  metrics:
    serviceMonitor: true
  inputTail:
    multiline.parser: [cri]
  filterKubernetes:
    K8S-Logging.Parser: "On"
    Merge_Log_Key: "parsed"
...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants