Karthik

Thank you for considering my issue as an enhancement. Since fluentd(Gem) is part of kube-fluentd-operator. Is there an idea to check for the health of fluentd(internal to kfo) as well?

Hi, Are there any plans to address this enhancement?

Sure, I can make a pull request. But I may need some help in testing it.

Hi, Can anyone please help me out with the issue that I am facing ?

@daipom Thanks for responding. The above Out_forward configuration is on the client side. Server side uses in_forward to receive it. When the server sends reset packet to forcefully close the...

@daipom, I do not have access to the server-side logs. I was just checking the output plugin documentation, If we make the tcp connection as long-lived/persistent i.e., my setting `keepalive:...

@daipom, ok sure, But I don't see CLOSE_WAIT connections getting closed. Am I missing any configuration that should be added?

Hi, Configuring keepalive_timeout helped me manage sockets in the CLOSE_WAIT state. However, I noticed that after setting keepalive_timeout, not only are inactive or CLOSE_WAIT sockets cleared, but all sockets are...

Thanks @Watson1978, @daipom, I tested with Fluentd version 1.16.6 and observed that the available/active sockets are not being closed, which is a good. However, I suspect there may be a...

Can anyone please help me out resolve the close_wait connection. Please let me know if any support is required to reproduce the issue. We can try to reproduce the issue...