Logspout is a log router for Docker containers that runs inside Docker. It attaches to all containers on a host, then routes their logs wherever you want. It also has an extensible module system. It's a mostly stateless log appliance. It's not meant for managing log files or looking at history. It is just a means to get your logs out to live somewhere else, where they belong. For now it only captures stdout and stderr, but a module to collect container syslog is planned. Logspout is a very small Docker container (15.2MB virtual, based on Alpine). The simplest way to use logspout is to just take all logs and ship to a remote syslog. Just pass a syslog URI (or several comma separated URIs) as the command. Here we show use of the tls encrypted transport option in the URI. You can tell logspout to ignore specific containers by setting an environment variable when starting your container.
Features
- You can tell logspout to only include certain containers by setting filter parameters on the URI
- You can route to multiple destinations by comma-separating the URIs
- You can tell logspout to only display log entries since container "start" or "restart" event
- You can connect with curl to see your local aggregated logs in realtime
- Logspout relies on the Docker API to retrieve container logs
- In order to enable multiline logging, you must first prefix your adapter with the multiline adapter
Project Samples
