Wesley Pettit

Relevant: https://gist.github.com/sumo-drosiek/c7b9d812cc3279062b0fe74e13aea64e https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/2564/files

This newly released feature inside of AWS for Fluent Bit serves the same use case and provides additional features: https://github.com/aws/aws-for-fluent-bit/blob/mainline/use_cases/init-process-for-fluent-bit/README.md You can pull multiple config files from S3 and also...

Hey @chikinchoi, there is a workaround that allows you to edit Mem_Buf_Limit right now, though it is slightly inconvenient. I am working on writing and publishing a short tutorial on...

@chikinchoi Sorry for the delay, here is the short tutorial (which will be improved and cleaned up and published elsewhere in some time). ### Background: How FireLens configures Fluentd and...

Let me know if any of it is confusing

@chikinchoi > I would like to append the Mem_Buf_Limit to the input plugin instead of overwriting the whole fluent-bit.conf. Is it still ok to do it with your solution? At...

I think a possibly good alternative to fixing this in FireLens would be a Service section configuration for Fluent Bit that governs that max memory used for buffering by all...

The detailed blog on the workaround has been published: https://aws.amazon.com/blogs/containers/how-to-set-fluentd-and-fluent-bit-input-parameters-in-firelens/ Other than that we don't have an updated ETA on this feature at this time.

@farazhv the log driver buffer limit is entirely different. `Mem_Buf_Limit` is for the buffer inside of Fluent Bit. The log driver buffer is before that. In FireLens, there are a...

@farazhv > Can we use the [Throttle filter](https://docs.fluentbit.io/manual/pipeline/filters/throttle) in fluent-bit if we set the [retry limit](https://docs.fluentbit.io/manual/administration/scheduling-and-retries) to no_retries since that would be a simpler alternative to implement than creating a...