-
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 parser does not work for Containerd #4508
Comments
It is fixed on master, but it isn't released yet. I tested it on master.
a.log:
Output:
|
@lecaros does 1.8.12 contain this fix? |
Hi @xiaoping8385, no, it's only available for the future 1.9 release. |
Just tried 1.9.0 have no errors in fluent-bit log but logs stopped. Config is:
Moreover debug logs full of:
|
@lecaros is that fixed in v1.9.0? cause I just tested and still not work, the same configuration as yours, but the result is like
|
I've just tried the test case from #4508 (comment), and it doesn't work. @nokute78, can you please confirm whether it works for you? |
The test case from #4508 (comment) didn't work from a7414f0 Note: The unit test of multiline on current master works correctly. Cc @edsiper |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the |
This issue was closed because it has been stalled for 5 days with no activity. |
Bug Report
Describe the bug
Hi there, I configure my fluent-bit as :
and
the initial container.log is like :
which I copied from the official doc sample.
As I was running it in containerd container, so the output log under /var/log/containers/ is like
I expected to see those mulitiline logs be concatenated but I only get the first mulitiline message been successfully handled and not the next.
the output was like:
To Reproduce
Run fluent-bit with above configuration
Expected behavior
both two multiline messages should be handled correctly
Screenshots
Your Environment
The text was updated successfully, but these errors were encountered: