#logstash

Anyone know how to troubleshoot this? [2018-08-29T07:14:47,371][ERROR][logstash.outputs.elasticsearch] Encountered a retryable error. Will Retry with exponential backoff {:code=>504, :url=>"https://0c555decfeca009e9df36b6a48758d13.us-west1.gcp.cloud.es.io:9243/_bulk"}

hey, I cant get haproxy to work infront of logstash(tcp). All I see is: "message" => "RPY 0 0 . 0 52\r\n" - "message" => "END\r\n".. etc

I'm using basically the same config as: https://gist.github.com/mrlesmithjr/5ee958df9c9...

hmm....I think my cluster was overloaded again. Someone flooded it with stuff.

I'm not a big fan of elasticsearch's rather opaque failure modes. :/

Good afternoon all

I am running into an issue with my logstash kafka input plugin config

If I specify a topic pattern of say "test*" logstash doesn't seem able to identify kafka topics to consume

I'm running logstash 6.4 and logstash-input-kafka (8.1.1)

Apologies if this is not the correct channel for this kind of request

I'm trying to install logstash-filter-translate v3.1.0 (because https://github.com/logstash-plugins/logstash-fi...)

but on logstash start I still see: Couldn't find any filter plugin named 'translate'. Are you sure this is correct? Trying to load the translate filter plugin resulted in this error: no such file to load -- logstash/filters/translate

I *think* this is because there's no file /.gem/specs/api.rubygems.org%443/quick/Marshal.4.8/logstash-filter-translate-3.1.0.gemspec (I'm comparing to another working system)

but have no idea if that's the right diagnosis and if so why the plugin install is not writing that file... help welcome!

I'm trying to read in from a Docker log file and write out to S3 with Logstash using the logstash-output-s3 plugin. It seems pretty straightforward, but it's not working and I'm not seeing anything at all in the logstash logs except for the server startup. Here's my config: https://pastebin.com/bpFFegZ0

Any thoughts?

And when I say it's not working, nothing is being exported to logstash

erm, nothing is being exported to S3.