Plugin does not handle idle disconnects in a timely fashion. Results in dropped logs about fluent-plugin-papertrail HOT 3 OPEN

I believe we are seeing this behaviour as well. @UserNotFound did you manage to figure out a workaround for your systems in the meantime?

from fluent-plugin-papertrail.

I believe we are seeing this behaviour as well. @UserNotFound did you manage to figure out a workaround for your systems in the meantime?

@jwreford99 Sorry for the delayed reply -- I had not found a fix other than to never stop logging 😄 I was planning on checking out other Syslog+TLS plugins which might actually be maintained (eg https://github.com/zarqman/fluent-plugin-syslog-tls or https://github.com/fluent-plugins-nursery/fluent-plugin-remote_syslog) before resorting to trying to fix it myself.

I was ecstatic to see your PR, though!!! When I have some time to dedicate to it, I'll give it a try.

Did you glean any information about whether we can expect movement on reviewing/merging your contribution?

from fluent-plugin-papertrail.

No afraid not, I did that PR just in case there were some maintainers still somewhat active on this project that might be able to review code but didn't want to write it themselves. We have been running a fork of this for a little while now and it hasn't completely solved all of the issues of dropped connections but it has solved a significant majority (and we think the remaining issues are due to connectivity issues).

I had also looked at other alternatives but found that https://github.com/fluent-plugins-nursery/fluent-plugin-remote_syslog didn't solve our problems appropriately because it batched up log messages of the same severity, leading to out of order logs that were of different severities. I had not been aware of https://github.com/zarqman/fluent-plugin-syslog-tls/tree/master at all, but it looks like it doesn't fulfil our purposes as it is not a buffered output plugin, this means there is no file queue and no concept of retries to PT which (given our experience with PT connectivity issues) is fairly essential. Given that we have ended up sticking with this plugin

from fluent-plugin-papertrail.