Logstash rest input plugin

This is a plugin for Logstash.

It allows you to call a rest API (that produces JSON currently) and send the resulting JSON in an logstash event.

The idea behind this plugins came from a need to read springboot metrics endpoint, instead of configuring jmx to monitor my java application memory / gc/ etc.

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.

Config Example

input{
	rest{
		urls => { "test1" => "http://localhost:11100/content/management/metrics"
		          "test2" => "http://localhost:21100/content/management/metrics"}
		interval => 60
		timeout  => 60
		type => "springboot-metrics"
	}
}

Output Example

{
                      "mem" => 572416,
                 "mem.free" => 263075,
               "processors" => 8,
                   "uptime" => 10450679,
          "instance.uptime" => 15409449,
           "heap.committed" => 572416,
                "heap.init" => 262144,
                "heap.used" => 309340,
                     "heap" => 3728384,
             "threads.peak" => 35,
           "threads.daemon" => 32,
                  "threads" => 35,
                  "classes" => 7918,
           "classes.loaded" => 7919,
         "classes.unloaded" => 1,
     "gc.ps_scavenge.count" => 9,
      "gc.ps_scavenge.time" => 74,
    "gc.ps_marksweep.count" => 2,
     "gc.ps_marksweep.time" => 125,
                 "@version" => "1",
               "@timestamp" => "2015-06-10T21:43:14.832Z",
                     "name" => "test1",
                     "host" => "myhost.com",
                      "url" => "http://localhost:11100/content/management/metrics",
                  "success" => true,
             "responseCode" => 200,
                     "type" => "springboot-metrics"
}

Documentation

Logstash provides infrastructure to automatically generate documentation for this plugin. We use the asciidoc format to write documentation so any comments in the source code will be first converted into asciidoc and then into html. All plugin documentation are placed under one central location.

• For formatting code or config example, you can use the asciidoc [source,ruby] directive
• For more asciidoc formatting tips, see the excellent reference here https://github.com/elasticsearch/docs#asciidoc-guide

Need Help?

Need help? Try #logstash on freenode IRC or the https://discuss.elastic.co/c/logstash discussion forum.

Developing

1. Plugin Developement and Testing

Code

• 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

bundle install

Test

• Update your dependencies

bundle install

• Run tests

bundle exec rspec

2. Running your unpublished Plugin in Logstash

2.1 Run in a local Logstash clone

• Edit Logstash Gemfile and add the local plugin path, for example:

gem "logstash-filter-awesome", :path => "/your/local/logstash-filter-awesome"

• Install plugin

bin/plugin install --no-verify

• Run Logstash with your plugin

bin/logstash -e 'filter {awesome {}}'

At this 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

You 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:

• Build your plugin gem

gem build logstash-filter-awesome.gemspec

• Install the plugin from the Logstash home

bin/plugin install /your/local/plugin/logstash-filter-awesome.gem

• Start Logstash and proceed to test the plugin

Contributing

All contributions are welcome: ideas, patches, documentation, bug reports, complaints, and even something you drew up on a napkin.

Programming 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.

It is more important to the community that you are able to contribute.

For more information about contributing, see the CONTRIBUTING file.