Closed purbon closed 7 years ago
This PR works as example of what could be a current usage of the slowlog implemented at https://github.com/elastic/logstash/pull/5886.
To test it you need to point the plugin to current changes hold into the logstash-core PR, this could be easy done by:
Step 2. could be done by modifying the plugin Gemfile with something like:
source 'https://rubygems.org' # Specify your gem's dependencies in logstash-mass_effect.gemspec gemspec gem "logstash-core", :path => "logstash/logstash-core" gem "logstash-core-event-java", :path => "logstash/logstash-core-event-java" gem "logstash-core-plugin-api", :path => "logstash/logstash-core-plugin-api"
This PR content might change if the API from core does.
since this PR was used as an example, I'm going to close it until interest in having plugin specific slowlog awareness appears again.
This PR works as example of what could be a current usage of the slowlog implemented at https://github.com/elastic/logstash/pull/5886.
To test it you need to point the plugin to current changes hold into the logstash-core PR, this could be easy done by:
Step 2. could be done by modifying the plugin Gemfile with something like:
Important
This PR content might change if the API from core does.