Logspout adapter for writing Docker container stdout/stderr logs to Redis in Logstash jsonevent layout.

See the example below for more information.

Logspout including this adapter is available on Docker Hub. Pull it with:

$ docker pull rtoma/logspout-redis-logstash

$ docker run -d --name logspout /var/run/docker.sock:/var/run/docker.sock:ro rtoma/logspout-redis-logstash redis://<your-redis-server>

Some configuration can be passed via container environment keys. Some can be appended as query parameters to the endpoint.

Behaviour of the adapter can be changed by passing configuration via docker environment vars (e.g. -e key=val).

• DEBUG=1: will enable logspout debug mode (default is disabled);
• REDIS_PASSWORD=<password>: will force the adapter to do an AUTH to Redis (default is none);
• REDIS_KEY=<key>: will configure the Redis list key to add events to (default is 'logspout');
• REDIS_DOCKER_HOST=<host>: will add a docker.host= field, allows you to add the hostname of your docker host, identifying where your container was running (think mesos cluster);
• REDIS_USE_V0_LAYOUT=1: logstash jsonevent layout v0 will be used (default is v1 layout).

Two keys can also be set as endpoint query parameters.

The REDIS_KEY can be set as redis://host?key=<key>.

The REDIS_USE_V0_LAYOUT switch can be set with ?use_v0_layout=1

Try out logspout with redis-logstash adapter in a full ELK stack. A docker-compose.yml can be found in the example/ directory.

When logspout with adapter is running. Executing something like:

docker run --rm centos:7 echo hello from a container

Will result in a corresponding event in Elasticsearch. Below is a screenshot from Kibana4:

Thanks to Gliderlabs for creating Logspout!

For other credits see the header of the redis.go source file.