logspout icon indicating copy to clipboard operation
logspout copied to clipboard

Log routing for Docker container logs

Results 111 logspout issues
Sort by recently updated
recently updated
newest added
trafficstars

Hello, I want to put my containers logs into my syslog server (running with syslog-ng). So I'm trying Logspout, and the logs are well sent to my syslog server. But...

Please update the README.md to include ROUTE_URIS in the environment variables and an invocation example. I only came across this with a search and found #217 and #90 my use...

Could anyone explain to me how to use `httpstream` with `multiline` support? As far as I understand `httpstream` is not considered as an adapter, but the docs say we need...

This was created as a way to pass a specific environment variable that's inside of the docker container. The variable .Container.Config.Env is formed of an array of key=value so it's...

type: enhancement
needs: rebase
needs: documentation
needs: tests

Appearantly you can force encryption when sending logs to Logentries by just changing the domain and port number, but this does not seem to work with logspout. First I've followed...

Documentation states: ``` Logspout relies on the Docker API to retrieve container logs. A failure in the API may cause a log stream to hang. Logspout can detect and restart...

Hi, I am trying to incorporate logspout in my environment, for I am using below settings in my docker compose file. ``` logspout: image: gliderlabs/logspout:v3.2.6 environment: SYSLOG_FORMAT: rfc3164 MULTILINE_MATCH: last...

I have a problem with logspout where we have seen it lose connection to our logging infrastructure and seemingly never even tries to reconnect. It seems in other similar issues...

I want to use multiline pattern per container, but currently it's only available as a global pattern. I can workaround by using multiple logspout, but it will be great if...

It appears that some of the changes in Docker to manage large log messages have resulted in logspout not passing them on. In previous versions, the log stream always ended...