Logstash - transport and process your logs, events, or other data
Find a file
debadair c22be7997a
[DOCS] Add EOL notice. (#11414)
* [DOCS] Add EOL notice. (#11410)

* [DOCS] Set version in EOL notice.
2019-12-10 14:57:53 -08:00
.github Move Contributors for more visibility 2016-05-20 16:58:58 +00:00
bin bubble up failed exit status 2017-10-12 11:25:42 -04:00
ci dynamically assign drive letter to WORKSPACE env var 2017-09-29 15:23:51 -04:00
config MINOR: Set Xms == Xmx as a default 2017-08-01 06:40:54 +00:00
data add data dir back 2017-05-30 20:29:18 +00:00
docs [DOCS] Add EOL notice. (#11414) 2019-12-10 14:57:53 -08:00
gradle/wrapper MINOR: Clean upgrade to Gradle 3.5 2017-06-05 06:50:24 +00:00
lib fixes for Windows platform tests/specs 2017-09-21 13:43:59 -04:00
logstash-core bump JrJackson/Jackson versions, source all version refs from versions.yml 2017-09-26 18:45:32 +00:00
logstash-core-plugin-api Bump from 5.5.3 -> 5.5.4 2017-09-13 15:58:05 +00:00
modules Fixed folder layout 2017-06-22 10:29:47 -07:00
pkg Truncate from the end of the message instead of the front. 2016-11-15 18:39:15 -05:00
qa Test fix: Allow slowlog to have >= 1 entries, instead of exactly 2 entries. 2017-09-19 21:54:44 +00:00
rakelib bump JrJackson/Jackson versions, source all version refs from versions.yml 2017-09-26 18:45:32 +00:00
spec fixes for Windows platform tests/specs 2017-09-21 13:43:59 -04:00
tools fix ingest test broken test on Windows 2017-09-21 14:14:21 -04:00
.dockerignore Introduce docker for CI builds. 2017-09-14 20:45:56 +00:00
.gitignore bump JrJackson/Jackson versions, source all version refs from versions.yml 2017-09-26 18:45:32 +00:00
.ruby-version Add .ruby-version 2017-09-21 14:14:21 -04:00
build.gradle Introduce docker for CI builds. 2017-09-14 20:45:56 +00:00
CONTRIBUTING.md Fix P1 definition to include test failures 2016-05-20 16:58:59 +00:00
CONTRIBUTORS ElasticSearch output plugin to support multiple hosts and enhance stability. (by Hao Chen) 2014-10-09 17:24:14 -07:00
Dockerfile 5x: Use 5x base image for 5x builds 2017-09-20 12:14:55 +00:00
Dockerfile.base 5x: Use 5x base image for 5x builds 2017-09-20 12:14:55 +00:00
dripmain.rb merge feature/java_persistence into 5.x 2016-10-31 17:03:40 -04:00
Gemfile.jruby-1.9.lock.release Bump from 5.5.3 -> 5.5.4 2017-09-13 15:58:05 +00:00
Gemfile.template Bump to 5.5.2 and update lock file (#7932) 2017-08-08 10:31:27 -07:00
gradle.properties Test fix: disable the gradle daemon by default (as recommended for CI) 2017-10-05 20:50:48 +00:00
gradlew Migrate Logstash to Log4j2 Logging (#5651) 2016-08-26 18:11:22 +00:00
gradlew.bat Migrate Logstash to Log4j2 Logging (#5651) 2016-08-26 18:11:22 +00:00
LICENSE Generate notice file during artifact build (#6538) 2017-01-16 10:10:18 -08:00
NOTICE.TXT Bump from 5.5.3 -> 5.5.4 2017-09-13 15:58:05 +00:00
Rakefile Rakefile: update help with test tasks. 2017-03-31 14:01:29 -04:00
README.md [DOCS] Build Logstash Reference from logstash repo (#9078) 2018-01-31 11:13:14 -08:00
ROADMAP.md New roadmap page 2016-05-20 05:59:42 +00:00
settings.gradle #7128 ingest json to grok js converter 2017-05-27 21:25:03 +00:00
STYLE.md Update STYLE.md 2016-03-11 16:49:35 +00:00
versions.yml bump JrJackson/Jackson versions, source all version refs from versions.yml 2017-09-26 18:45:32 +00:00

Logstash

Build status

Test master 5.0 2.4
core Build Status Build Status Build Status

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

Documentation and Getting Started

You can find the documentation and getting started guides for Logstash on the elastic.co site

For information about building the documentation, see the README in https://github.com/elastic/docs

Downloads

You can download Logstash binaries, as well as debian/rpm packages for the supported platforms, from downloads page.

Need Help?

Logstash Plugins

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.

Writing your own Plugin

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

Plugin Issues and Pull Requests

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.

Developing Logstash Core

Prerequisites

  • Install JDK version 8
  • Install JRuby 1.7.x.
  • Install rake and bundler tool using gem install rake and gem install bundler respectively.

On Windows make sure to set the JAVA_HOME environment variable to the path to your JDK installation directory. For example set JAVA_HOME=<JDK_PATH>

Vendored JRuby: Logstash uses JRuby which gets embedded in the vendor/jruby/ directory. It is recommended to use a Ruby version manager such as RVM or rbenv.

  • To run Logstash from the repo you must first bootstrap the environment:
rake bootstrap
  • You can then use bin/logstash to start Logstash, but there are no plugins installed. Logstash ships with default plugins. To install those, you can run:
rake plugin:install-default
  • Alternatively, you can only install the core plugins required to run the tests
rake test:install-core

To verify your environment, run

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 world

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.

Testing

For testing you can use the test rake tasks and the bin/rspec command, see instructions below. Note that the bin/logstash rspec command has been replaced by bin/rspec.

Core tests

1- In order to run the core tests, a small set of plugins must first be installed:

rake test:install-core

2- To run the logstash core tests you can use the rake task:

rake test:core

or use the rspec tool to run all tests or run a specific test:

bin/rspec
bin/rspec spec/foo/bar_spec.rb

Plugins tests

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 or all plugins:

rake test:install-default
rake test:install-all

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

Building Artifacts

You can build a Logstash snapshot package as tarball or zip file

rake artifact:tar
rake artifact:zip

This 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

Project Principles

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

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 me that you are able to contribute.

For more information about contributing, see the CONTRIBUTING file.