João Duarte

@lior-orca thanks for the contribution! please make sure that the email you used to sign the CLA is the same used in the git commit: https://patch-diff.githubusercontent.com/raw/elastic/logstash/pull/14423.patch, and that the email...

This PR would implement the enhancement request from https://github.com/elastic/logstash/issues/11601

how to reproduce: ``` input { generator { count => 1 message => "2015-02-11T17:49:29Z logspout dev_ziservice_1[1]: ASDF"} generator { count => 1 message => "2015-02-11T17:49:29Z logspout dev_ziservice_1[1]: "} generator {...

1) I believe first we can implement capturing of metrics per grok match 2) from there we could expose an option to automatically reorganize the patterns. However this cannot be...

On a note: JRuby 9.0.5.0 performs similarly, if not slightly faster (after working around https://github.com/jruby/jruby/issues/3715): ``` main profile results: Total time: 88.77 total self children calls method ---------------------------------------------------------------- 88.77 0.46...

On a side note, big props to @colinsurprenant for the logstash-core-event-java. In my tests using the old ruby version of logstash-core-event made the []/[]= methods take a bigger slice of...

Isn't this done now in https://github.com/ruby-amqp/march_hare/blob/ffa01c25c69a7b4077092963b5f8960184884f39/lib/march_hare/session.rb#L72-L104?

@jordansissel agreed this is not a very common scenario. I wonder if a simple "hey I see you set sincedb path, be careful because..." And yes, good point wrt to...

this has been solved in https://github.com/logstash-plugins/logstash-output-s3/pull/179, can you update the plugin and confirm?

We're exploring ways to both fix this and workaround it until a fix is out. In the case of this plugin we don't have much access to how the AWS...