logspout-logstash icon indicating copy to clipboard operation
logspout-logstash copied to clipboard

A minimalistic adapter for github.com/gliderlabs/logspout to write to Logstash

Results 12 logspout-logstash issues
Sort by recently updated
recently updated
newest added

Using RAW_FORMAT to include docker labels gives an error in logstash and document is written. Really want docker labels. Any idea how to fix this? ``` version: '3.3' services: logspout:...

I was using a dockerhub image that is a self-contained ELK stack. I was trying to run the ELK stack and Logspout-Logstash from a single docker-compose.yml. Seems that if the...

I'm not seeing the 'severity' (e.g. DEBUG, INFO, ERROR, etc) tag being included in logspout-logstash messages. Is there a configuration option I'm missing or is this not supported yet?

I've followed the instructions listed here and on the original logspout repository, but I appear to be having problems finding the logspout-logstash dependency (both locally and on CI) The error...

I wanted to add some custom fields to my logspout-generated events. The Readme says: > You can also add arbitrary logstash fields to the event using the LOGSTASH_FIELDS container environment...

We are experiencing issues with High CPU usage on dockerd whenever we enable the logspout-logstash container. More details on [this](https://github.com/gliderlabs/logspout/issues/246) issue report

When logging JSON numbers from docker, ex:`{"value":1000000}` the value is converted to scientific notation once it's gone through the Marshall/Unmarshalling. ie:`{"value":1e+06}` While this is not technically incorrect, it prevents us...

I'm occasionally seeing the following error log in my logspout container, which causes it to exit. ``` logstash: could not write:write tcp 172.17.0.2:49194->192.168.1.178:5001: write: connection reset by peer ``` Port...

``` ... Executing busybox-1.24.2-r0.trigger Executing ca-certificates-20160104-r2.trigger OK: 401 MiB in 48 packages # github.com/go-check/check ../../go-check/check/error.go:4: "ERROR: the correct import path is gopkg.in/check.v1 ... " evaluated but not used The command...

Could you think of adding another field for the node (or hostname of the docker engine) the container is running on? This would be very helpful for docker swarm clusters.