Name: logstash-filter-jdbc_static
Owner: Logstash Plugins
Description: Loads a DB query's result set in memory and uses it as lookup table for events.
Created: 2017-01-08 20:57:47.0
Updated: 2018-05-22 10:43:00.0
Pushed: 2018-05-21 13:07:18.0
Size: 117
Language: Ruby
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
Lookup plugin which overwrites a loader query's result set into a local in-memory db and then lookup queries add records to a target field using properties from the event.
This is a plugin for Logstash.
It is fully free and fully open source. The license is Apache 2.0, meaning you are pretty much free to use it however you want in whatever way.
Need help? Try #logstash on freenode IRC or the https://discuss.elastic.co/c/logstash discussion forum.
To get started, you'll need JRuby with the Bundler gem installed.
Create a new plugin or clone and existing from the GitHub logstash-plugins organization. We also provide example plugins.
Install dependencies
le install
le install
le exec rspec
Gemfile
and add the local plugin path, for example:"logstash-filter-awesome", :path => "/your/local/logstash-filter-awesome"
gstash 2.3 and higher
logstash-plugin install --no-verify
bin/plugin install –no-verify
n Logstash with your plugin
bin/logstash -e 'filter {awesome {}}'
his point any modifications to the plugin code will be applied to this local Logstash setup. After modifying the plugin, simply rerun Logstash.
2.2 Run in an installed Logstash
can use the same **2.1** method to run your plugin in an installed Logstash by editing its `Gemfile` and pointing the `:path` to your local plugin development directory or you can build the gem and install it using:
ild your plugin gem
gem build logstash-filter-awesome.gemspec
stall the plugin from the Logstash home
bin/logstash-plugin install –no-verify
bin/plugin install –no-verify
art Logstash and proceed to test the plugin
ontributing
contributions are welcome: ideas, patches, documentation, bug reports, complaints, and even something you drew up on a napkin.
ramming is not a required skill. Whatever you've seen about open source and maintainers or community members saying "send patches or die" - you will not see that here.
s more important to the community that you are able to contribute.
more information about contributing, see the [CONTRIBUTING](https://github.com/elastic/logstash/blob/master/CONTRIBUTING.md) file.