-
I am trying to run logspout on a server that has 20+ containers. Every time I start the logspout container, the core CPU's shoot up from 90% and eventually the server crashes. I even added a filter so…
-
1、Logspout collects container log with sincetime. Once the process exits and starts again, there will be log loss before logspout restarts. So I wonder that logspout can persist the sincetime, then th…
saiwl updated
7 years ago
-
Bit of an edge case here...
I was looking into using [logspout](https://github.com/progrium/logspout) to get the ELK stack running, but the way it is implemented has some interesting limitations. Bec…
-
Hi, we've having constant errors in the logs when starting this container.
```
...more
2020/07/24 16:29:22 http[logs,routes]:80 ended: listen tcp 0.0.0.0:80: bind: address already in use,
# logs…
-
hi guys,
we are really looking forward to multi-line support. any chance of getting that since the upstream logspout has already built support for that
-
It would be nice to be able to pass in an env var like `SYSLOG_ENDPOINT` and have that be used with the syslog command. Example:
```
sudo docker run --name='logspout' --restart=always \
-d -v=/var/…
-
## Background
The `github.com/gliderlabs/logspout` uses [Go modules](https://github.com/golang/go/wiki/Modules) and the current release version is `v3`. And it’s module path is `"github.com/gliderlab…
-
Hi, I'm getting this error about missing port even though I am providing port (see 10000 below)
```
$ docker run --name="logspout" \
--volume=/var/run/docker.sock:/var/run/docker.sock \
…
-
We have an nginx container that accepts hundreds of request per second and logspout is causing our CPU to burst with the stream of logs it produces. We already applied:
```
TAIL=0
BACKLOG=true
`…
-
I tried to start a container from the image using the suggested command:
```
docker run --env DEBUG=1 --name="logspout" \
--volume=/var/run/docker.sock:/tmp/docker.sock \
--publish=0.0.0.0:80…