-
Notifications
You must be signed in to change notification settings - Fork 104
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
[Feature request] Setting Mem_Buf_limit of td-agent-bit #572
Comments
The default value of Mem_Buf_Limit is so small that logs can be lost in the event of a temporary increase in traffic. |
@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). |
Logs are necessary for business and system operations, so we want them to be written to LogAnalytics without loss. |
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. |
@daweim0 Thank you for your quick review and merge! Great! |
I confirmed roll-out with creating new cluster. So I will close this issue. Thank you for your cooperation. |
In an AKS environment, logs are lost in an environment where a large amount of logs are output from containers.
I forced myself to change Mem_Buf_limit from its default value in the container of omsagent's DaemonSet, and this improved the situation.
It would be very helpful if the Mem_Buf_limit setting of td-agent-bit could be changed using ConfigMap.
The text was updated successfully, but these errors were encountered: