-
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
Forward input + multi-line parser consumes more than 100% CPU and lost of enriched data #8702
Comments
Maybe related: #8473 |
Does it make a difference, when you disable the multiline or/and the regex filter? Can you isolate the issue further? |
@drbugfinder-work FYI I tried the newest version 3.0.2 and can observe the same issues:
Regarding your question about the multiline parser/regex, the issues appear only with forward input, because with the tail input everything is working well |
hey @drbugfinder-work I was running the same scenario (with the latest 3.0.2) on my Macbook Air (much less power than my workstation) and did not see the issues (the CPU usage stays low and the enriched data are present in the output). |
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
During the evaluation of Fluent Bit, I am trying to have the following architecture (critical for our use case):
|fluent-bit-shipper| -> |fluent-bit-aggregator| -> |final destination|
But I got those 2 blocking issues:
Everything (configurations, instructions to reproduce, observations) provided here:
(I also shared this issue with Eduardo and Anurag as they asked)
Thanks for your help & feedback
The text was updated successfully, but these errors were encountered: