logspout
logspout copied to clipboard
gliderlabs
Log routing for Docker container logs
After upgrading to 3.2.3 logspout started adding weird characters to the beginning of every line. For example ``` �time="2017-10-04T01:20:14Z" level=info msg="Done checkpointing in-memory metrics and chunks in 1.404599334s." source="persistence.go:665" xtime="2017-10-04T01:25:14Z"...
With https://github.com/gliderlabs/logspout/commit/e0d92638b3f8e8eea4c5683498b9364b7e8e9050 you untroduced a "feature" which removes the first 8 Bytes from the log message. router/pump.go ` if hasHeaders { buf.Discard(8) } ` Unfortunately hasHeaders will always be true...
We recently upgraded to Logspout `v3.2` from `v2`, and many things are better. We have it running on a machine which runs jobs on cron twice a day. We noticed...
Hi, given SYSLOG_TAG/HOSTNAME is set to templates via the env variable like this: ``` SYSLOG_TAG='{{ index .Container.Config.Labels "io.kubernetes.pod.namespace" }}[{{ index .Container.Config.Labels "io.kubernetes.pod.name" }}]' SYSLOG_HOSTNAME='{{ index .Container.Config.Labels "io.kubernetes.container.name" }}' ``` logspout...
I'm trying to run logspout to put my logs in Papertrail without much luck. Here's the output of `docker logs logspout`: ``` # logspout v3.1 by gliderlabs # adapters: udp...
`{{.Timestamp}}` doesn't seem to work in raw mode, but I believe Docker does record a timestamp on each log because Docker Cloud somehow shows one. What is the technical limitation...
If your company or project is using Logspout or some variation, please list yourself below!
@imriz did a great job of summarizing this exact issue (and his fix) in bullet point 4 of his comment on #215 ([comment](https://github.com/gliderlabs/logspout/issues/215#issuecomment-267975980)) To summarize, I have logs being sent...
Some strange issue since upgrade to v3.2 or latest version. We are using logspout with kubernetes daemonset and logstash. Recently we realized logstash was not sending complete logs of container...
During logspuot start if the connection to the log server fails (papertrail, BTW) the container fails to start ``` $ docker run -p 8000:8000 -v=/var/run/docker.sock:/tmp/docker.sock gliderlabs/logspout:latest tcp+tcl://yyyyyy.papertrailapp.com:xxPORTxx # logspout v3.2.2...
