-
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
Tail input with multi-line and exit_on_eof broken in 1.6.x #2668
Comments
I also have problems with Those two lines that are read are also reported as one event I have
|
I've tried again with 1.6.2: the problem is the same... |
I've tried again with 1.6.4: the problem is the same... |
Signed-off-by: Eduardo Silva <[email protected]>
Signed-off-by: Eduardo Silva <[email protected]>
Signed-off-by: Eduardo Silva <[email protected]>
Signed-off-by: Eduardo Silva <[email protected]>
the following fixes have been applied
the main problem was that on hard exit (exit on eof) the pending buffers of in_tail were not flushed |
I tried to reproduce your problem but was not possible, @LionelCons issue was different. the following is my config:
file sample_1.log content
file sample_2.log content
Fluent Bit Output
if you are still able to reproduce the issue, please open a new Github issue and reference this one so we can troubleshoot. I am closing this ticket since the primary issue is fixed. |
The newly released 1.6.0 does not work like before when using multi-line and
exit_on_eof
.Consider the following input:
And the following configuration:
When using 1.6.0 (and
Read_From_Head
to have the same behaviour as before) we get:So we miss the third line.
Without
Exit_On_EOF
, we do get the third line.In contrast, with 1.5.6, with
Exit_On_EOF
, we get:So we do get the third line.
The text was updated successfully, but these errors were encountered: