gliderlabs/logspout
Log routing for Docker container logs observed · 2026-08-28
Health v2 · maintenance only
23/100
- Activity 0
- Release rhythm 8
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4495
- days_rel: n/a
- days_push: 1149
- n_releases_24m: 0
Adoption not part of the score
4689 stars · 662 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Logspout is a log router for Docker containers that runs inside Docker, attaching to all containers on a host and routing their stdout/stderr logs to remote destinations like syslog. It is a small, mostly stateless log appliance with an extensible module system.
Use cases
- ship docker container logs to remote syslog
- route all container stdout and stderr to a log aggregator
- send docker logs to papertrail over tls
- collect logs from all containers on a host
- ignore specific containers when shipping logs
When to choose
- you want a tiny stateless container that forwards docker logs elsewhere
- you use syslog-compatible log destinations
- you need an extensible log routing appliance for docker
When to avoid
- you need log history, storage, or log file management
- you need to capture container syslog rather than stdout/stderr
- you need advanced log processing or filtering
Facets
application · maturity maintenance
logging monitoring monitoring go self-hosted docker-logs log-shipping syslog log-router devops containers docker linux
1 source
- readme: https://github.com/gliderlabs/logspout · fetched 2026-08-28 · 659f45e4ffe1
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| gliderlabs/logspout | main | 23 |
For agents
markdown · JSON · MCP: product_card(name="gliderlabs/logspout")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem