Open cjohansen opened 7 years ago
The logspout container doesn't have any more logs. Where can I find some information about logspout's attempts to send logs to papertrail?
I assumed that all the filters supported a comma-separated list of containers. Turns out this is not the case, so the above filter actually filters on container with name "myapp1,myapp2", instead of the two intended containers. Worked around this with labels instead. I would suggest making this limitation on filter.name
explicit in the Readme (or supporting a comma-separated list of names for filter.name).
I agree it would be preferable to support a comma separated list. I haven't been in that part of the code yet but I'd be interested to see a PR for this change.
@cjohansen how did you started the logspout? When I run it as:
docker run --restart=always --name logspout --hostname logspout -d -v=/var/run/docker.sock:/var/run/docker.sock gliderlabs/logspout:master syslog://logs6.papertrailapp.com:$PORT
works for me.
I'm trying to run logspout to put my logs in Papertrail without much luck. Here's the output of
docker logs logspout
:Which looks right to me. Tailing the log locally over http (e.g.
curl http://localhost:8000/logs
) shows me the relevant log messages. However, with the 3.2.1 container, all I could see in Papertrail was a whole bunch of these:Looks like the same thing that was reported https://github.com/gliderlabs/logspout/issues/246#issuecomment-286284186, so I tried the recommendation there, running v3.1 instead. With 3.1 the error goes away, but I still do not see a single log statement in Papertrail (the http endpoint is still logging messages as expected). Am I holding it wrong?