Logspout container for Docker and Loggly.
You can build the image yourself
docker build -t your-user-name/logspout-loggly ./
and, optionally, push it to your own hub.docker.com repo
docker push your-user-name/logspout-loggly
or you can pull a prebuilt image
docker pull iamatypeofwalrus/logspout-loggly
How to run
docker run -d \ -e 'LOGGLY_TOKEN=<token>' \ -e 'LOGGLY_TAGS=<comma-delimited-list>' \ -e 'FILTER_NAME=<wildcard-container-name>' \ --volume /var/run/docker.sock:/tmp/docker.sock \ iamatypeofwalrus/logspout-loggly
How it works
Instead of linking containers together or bothering with syslog or remote syslog this container follows the 12 Factor app logging philosophy. If your docker container(s) log(s) to STDOUT this image will pick up that stream from the docker daemon send those events to Loggly.
pretty cool, and the output actually is broken in fields in Loggly.
How could we get a message about the (re)start of this container into the output stream? I now see all containers in my deployment, except this one.