Logstash is part of the Elastic Stack along with Beats, Elasticsearch and Kibana. Logstash is an open source, server-side data processing pipeline that ingests data from a multitude of sources simultaneously, transforms it, and then sends it to your favorite "stash." (Ours is Elasticsearch, naturally.). Logstash has over 200 plugins, and you can write your own very easily as well.
The license is Apache 2.0, meaning you are pretty much free to use it however you want in whatever way.
For more info, see https://www.elastic.co/products/logstash
You can find the documentation and getting started guides for Logstash on the elastic.co site
You can download officially released Logstash binaries, as well as debian/rpm packages for the supported platforms, from downloads page.
For the daring, snapshot builds are available. These builds are created nightly and have undergone no formal QA, so they should never be run in production.
| artifact |
|---|
| tar |
| zip |
| deb |
| rpm |
- Logstash Forum
- Logstash Documentation
- #logstash on freenode IRC
- Logstash Product Information
- Elastic Support
Logstash plugins are hosted in separate repositories under the logstash-plugins github organization. Each plugin is a self-contained Ruby gem which gets published to RubyGems.org.
Logstash is known for its extensibility. There are hundreds of plugins for Logstash and you can write your own very easily! For more info on developing and testing these plugins, please see the working with plugins section
Please open new issues and pull requests for plugins under its own repository
For example, if you have to report an issue/enhancement for the Elasticsearch output, please do so here.
Logstash core will continue to exist under this repository and all related issues and pull requests can be submitted here.
- Install JDK version 8. Make sure to set the
JAVA_HOMEenvironment variable to the path to your JDK installation directory. For exampleset JAVA_HOME=<JDK_PATH> - Install JRuby 9.1.x It is recommended to use a Ruby version manager such as RVM or rbenv.
- Install
rakeandbundlertool usinggem install rakeandgem install bundlerrespectively.
If you prefer to use rvm (ruby version manager) to manage Ruby versions on your machine, follow these directions:
gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
\curl -sSL https://get.rvm.io | bash -s stable --ruby=jruby-9.1.10.0Before you proceed, please check your ruby version by:
$ ruby -v
jruby 9.1.10.0 (2.3.3) 2017-05-25 b09c48a Java HotSpot(TM) 64-Bit Server VM 25.131-b11 on 1.8.0_131-b11 +jit [darwin-x86_64]- To run Logstash from the repo you must first bootstrap the environment:
rake bootstrap- You can then use
bin/logstashto start Logstash, but there are no plugins installed. To install default plugins, you can run:
rake plugin:install-defaultThis will install the 80+ default plugins which makes Logstash ready to connect to multiple data sources, perform transformations and send the results to Elasticsearch and other destinatins.
To verify your environment, run the following to send your first event:
bin/logstash -e 'input { stdin { } } output { stdout {} }'This should start Logstash with stdin input waiting for you to enter an event
hello world
2016-11-11T01:22:14.405+0000 0.0.0.0 hello worldAdvanced: Drip Launcher
Drip is a tool that solves the slow JVM startup problem while developing Logstash. The drip script is intended to be a drop-in replacement for the java command. We recommend using drip during development, in particular for running tests. Using drip, the first invocation of a command will not be faster but the subsequent commands will be swift.
To tell logstash to use drip, either set the USE_DRIP=1 environment variable or set JAVACMD=`which drip`.
Example:
USE_DRIP=1 bin/rspec
Caveats
Drip does not work with STDIN. You cannot use drip for running configs which use the stdin plugin.
Most of the unit tests in Logstash are written using rspec for the Ruby parts. For the Java parts, we use junit. For testing you can use the test rake tasks and the bin/rspec command, see instructions below:
1- To run the core tests you can use the Gradle task:
./gradlew test
or use the rspec tool to run all tests or run a specific test:
bin/rspec
bin/rspec spec/foo/bar_spec.rb
Note that before running the rspec command for the first time you need to set up the RSpec test dependencies by running:
./gradlew bootstrap
2- To run the subset of tests covering the Java codebase only run:
./gradlew javaTests
3- To execute the complete test-suite including the integration tests run:
./gradlew check
To run the tests of all currently installed plugins:
rake test:plugin
You can install the default set of plugins included in the logstash package:
rake test:install-default
Note that if a plugin is installed using the plugin manager bin/logstash-plugin install ... do not forget to also install the plugins development dependencies using the following command after the plugin installation:
bin/logstash-plugin install --development
You can build a Logstash snapshot package as tarball or zip file
rake artifact:tar
rake artifact:zipThis will create the artifact LS_HOME/build directory
You can also build .rpm and .deb, but the fpm tool is required.
rake artifact:rpm
rake artifact:deb- Community: If a newbie has a bad time, it's a bug.
- Software: Make it work, then make it right, then make it fast.
- Technology: If it doesn't do a thing today, we can make it do it tomorrow.
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 me that you are able to contribute.
For more information about contributing, see the CONTRIBUTING file.