👍

hey all we get it you want this, but can you not +1, because it makes feedback hard to read :), we promise we will do our best to review this as soon as possible

adding this seems fine to me, will wait for others to approve then we can move into code-review if so :)

@jfrazelle Just a background. @tagomoris is a maintainer of Fluentd (http://www.fluentd.org/), and I'm from Treasure Data, Inc. sponsoring Fluentd project.

Docker + Fluentd adopted by Google & Kubernetes

We recently started seeing more people adopting Docker + Fluentd. For example. Google's Kubernetes adopted Fluentd as a default log collector. But Kubernetes uses Fluentd's 'tail' input plugin for log files. It's not performant, reliable, and config files become relatively messy...

• https://github.com/GoogleCloudPlatform/kubernetes/tree/master/cluster/addons/fluentd-elasticsearch

FYI: Google adopted Fluentd as a default log collector for the entire cloud platform (packaging repo, bigquery documentation).

Docker + Fluentd by Digital Ocean

Digital Ocean wrote a documentation about how to centralize Docker logs into one place, using Fluentd. But as I mentioned above, it tails log files as well.

• https://www.digitalocean.com/community/tutorials/how-to-centralize-your-docker-logs-with-fluentd-and-elasticsearch-on-ubuntu-14-04

Push logs directly from Docker to Fluentd (Code is available)

We'd like to have a way to directly push the logs from Docker to Fluentd, which is more performant, reliable, and simple. Just in case, @tagomoris already wrote a code so that you can review.

• tagomoris@a05d082

Logging is the essential part of the immutable infrastructure, so hope Docker has a flexible way to centralized logs using the solution like Fluentd.

👍

Definitely +1 as long as we can ping for issues. @tagomoris @kzk do you plan to contribute code for this?
Also, proposal doc is probably longer than the actual implementation will be :)

I already have a complete code for this feature.
So I've just created a pull request #12876.

can you then combine this with that one so there are not two threads for the same feature and close this one

@cpuguy83 I can give you our point of contacts for you. Please reach out to me at [email protected]. Of course just mentioning on github works too.

I think we can close this, because now it is real PR #12876