-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Multiline functionality issue was solved by enabling docker_mode_parser, but after enabling the option i see kubernetes labels are missing from log output #2359
Comments
I am also seeing this with the below configuration:
Using 1.5.2 |
For me it works in version 1.5.7, but the regular expression does not meet the expectations for my scenario. Below is an excerpt from my sample log file.
My result is:
My custom_parsers.conf:
My fluent-bit.conf:
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Multiline UpdateAs part of Fluent Bit v1.8, we have released a new Multiline core functionality. This new big feature allows you to configure new For now, you can take at the following documentation resources:
Documentation pages now point to complete config examples that are available on our repository. Thanks everyone for supporting this! |
Bug Report
Describe the bug
<--- Multiline functionality issue was solved by enabling docker_mode_parser, but after enabling the option i see kubernetes labels are missing from log output. I was using the image 1.3.1 where i have having issues with multiline functionality and able to solve it by upgrading the image to 1.5.0 by enabling docker_mode_parser. But, after upgrading I see its missing kuberenetes labels -->
Log Sample
After enabling docker_mode_parser and docker_mode with image 1.5.0 i see missing kubernetes labels.
Here is the configuration i'm using. After changing the image to 1.5.0, i'm removing Multiline and adding Docker_Mode_Parser option to below configuartion
The text was updated successfully, but these errors were encountered: