João Duarte
João Duarte
Migrated from https://github.com/elastic/logstash/issues/7281 Created by @ror6ax ----- I'm having an issue with grok. I've wrote a string to match `10.155.16.115 - - [30/May/2017:08:53:41 +0000] "GET /sqi HTTP/1.1" 404 16 "-"...
running the specs fail for `logstash-core >= 2.2` ``` /tmp/logstash-filter-grok (git)-[master] % bundle exec rspec Using Accessor#strict_set for specs NoMethodError: undefined method `pattern_path' for LogStash::Environment:Module Grok at /private/tmp/logstash-filter-grok/lib/logstash/filters/grok.rb:226 (root) at...
test script: ``` ruby # encoding: utf-8 require 'logstash/event' require 'logstash/environment' require 'spec/filters/grok_spec' grok_base = LogStash::Filters::Grok.new( "match" => ["message", '%{IPORHOST:clientip} %{USER:ident} %{USER:auth} \[%{HTTPDATE:timestamp}\] "%{WORD:verb} %{DATA:request} HTTP/%{NUMBER:httpversion}" %{NUMBER:response:int} (?:-|%{NUMBER:bytes:int}) %{QS:referrer} %{QS:agent}'])...
Total time to process the same apache log line 1_000_000 times with `%{COMMONAPACHELOG}`: 93.88s (~10k e/s) The 6 biggest time offenders use 70.46s - 75% of total time: | Action...
In MRI 2.6: ``` % ruby -v ruby 2.6.0p0 (2018-12-25 revision 66547) [x86_64-darwin18] % ruby -e 'puts "foo========:bar baz================================================bingo".scan(/(?:=+=+)+:/)' ========: ``` With Latest JRuby snapshot: ``` /tmp/jruby-9.2.8.0-SNAPSHOT % java -version...
Historically we created the sincedb tracking file in the users home directory, but since we now default to `path.data/plugins/file` it doesn't make sense for it to be hidden anymore. in...
Currently in the documentation we warn that, when using more than one `file { }` section, you need different sincedb paths ([doc here](https://github.com/logstash-plugins/logstash-input-file/blob/master/lib/logstash/inputs/file.rb#L42)). However, we should enforce this somehow to...
The first time sincedb is written, it prints an error message, but works. Test scenario below: config: ``` input { file { path => "c:\test\teste.txt" start_position => "beginning" sincedb_path =>...
Currently the response body is either the string "ok", or nothing if the `response_code` is set to 204 (no content). There should be an option to configure a different static...
Starting the plugin with `input { http { password => 'hello'} }` will not enable auth and also raise no warning or error that both username and password are needed...