[Feature request] Setting Mem_Buf_limit of td-agent-bit about docker-provider HOT 6 CLOSED

@tsubasaxZZZ Thank you very much for submitting a patch to add this feature, we'll review it in the next few days. Just to set expectations properly, it takes about a month for updates to become available in all regions (so don't hold your breath waiting for this feature).

from docker-provider.

The default value of Mem_Buf_Limit is so small that logs can be lost in the event of a temporary increase in traffic.
In fact, in our project, even though the node's CPU, memory, network, and other resources have sufficient reserves, there was an event in which logs could not be transferred to Log Analytics and logs were missing.
Since Mem_Buf_Limit has become a fixed value, currently, the only thing that can be done to prevent the log from being lost is to increase the number of nodes.

from docker-provider.

Logs are necessary for business and system operations, so we want them to be written to LogAnalytics without loss.
If the configuration values can be changed, I want to manage them in ConfigMap like other settings in k8s.
I'm looking forward to it.

from docker-provider.

PR is merged, thank you again for the fix. I think it will go out in the next few weeks. @tsubasaxZZZ can I close this issue?

Just keep in mind that increasing the buffer size here will not increase the container memory limit. Also increasing the container memory limit and request might be a good idea, although this is only possible when onboarding though the helm.

from docker-provider.

@daweim0 Thank you for your quick review and merge! Great!
For my issue management, could you open it until the rollout is completed and I can check it on AKS?

from docker-provider.

I confirmed roll-out with creating new cluster. So I will close this issue. Thank you for your cooperation.
And I create new PR to sample ConfigMap. Please review and merge.
#606

from docker-provider.