We're seeing issues with logspout-fluentd where connectivity is never re-established with fluentd if it is lost, what we see instead is continuous logging of broken pipe messages in stderr, which causes a large spike in CPU activity on that docker host:

2018/01/09 15:07:31 fluentd-adapter: write tcp 127.0.0.1:38830->127.0.0.1:24224: write: broken pipe

We're running logspout in a container on each of our Rancher hosts talking to a separate container running fluentd. This issue requires us to restart the logspout container to re-establish connection. I saw a similar issue raised for the syslog logspout adapter: gliderlabs/logspout#107 in which they raised gliderlabs/logspout#291 to resolve the issue by adding a configurable number of reconnection attempts.

We much prefer the richness of the logging using logspout-fluentd over syslog, so would it be possible to implement a similar fix to the fluentd adapter?

Hi!
Thanks for this plugin, my team is using it as part of our logging pipeline

I was wondering if there was a way to add more metadata to log records before sending them to fluentd?
For example, container labels, or any container/service/stack/node information available from the API.
Currently, only timestamp, log, container_id and container_name fields seem to be included.
Maybe this is something that can be addressed "upstream" in the logspout project directly?
I've created an issue there too: gliderlabs/logspout#483.

If doing so would require modifying the code, I'm open to trying my hands at it eventually(I haven't coded in go yet, but it seems like a nice language), and submitting a PR, if I can get some pointers on what would need to be done.

Thanks again!