Logstash - transport and process your logs, events, or other data
Find a file
2015-01-27 23:59:17 +00:00
acceptance_spec More fixes 2014-12-03 17:04:10 +00:00
bin Make sure the vendorized jruby only have 1.9 libs, so no extra space is used. Also make sure the jruby is run in 1.9 mode. 2015-01-05 15:50:17 +00:00
bot Warm welcome to bot,may it serves you well 2013-03-11 07:13:54 +01:00
docs Incorporated Suyog's feedback. 2015-01-20 19:19:30 +00:00
lib allow uninstalling gems with bundler 2015-01-27 22:02:23 +00:00
locales fix merge conflicts 2015-01-21 22:08:12 +00:00
patterns removes the patterns from patterns dir 2014-12-17 19:40:38 +00:00
pkg fix nologin path 2015-01-05 22:55:03 +00:00
rakelib fix a typo on the test all plugins rake task 2015-01-27 17:17:22 +00:00
spec Use the .info level when printing the version notice for the plugin 2015-01-27 17:40:39 +00:00
test/jenkins remove integration test that has been move into its own gem 2014-12-19 10:26:03 +00:00
tools Skip some plugins 2015-01-27 23:59:17 +00:00
.gitignore do not ignore .lock files 2014-12-10 23:48:18 +00:00
.tailor - add .tailor config 2012-12-03 16:04:27 -08:00
CHANGELOG Added performance improvements 2014-12-09 21:37:11 +00:00
CONTRIBUTING.md Reference github issues now. 2014-07-14 22:21:37 -04:00
CONTRIBUTORS ElasticSearch output plugin to support multiple hosts and enhance stability. (by Hao Chen) 2014-10-09 17:26:24 -07:00
dripmain.rb logstash boot sequence cleanup & drip support fix 2014-07-13 20:09:40 -04:00
LICENSE Update License 2014-11-07 13:13:03 +00:00
logstash-event.gemspec fix logstash-event.gemspec for jruby and mri 2015-01-26 21:12:38 +00:00
logstash.gemspec update jar_dependencies 2015-01-27 20:26:46 +00:00
Makefile Refactor build tooling to use Ruby 2014-10-22 17:04:58 +00:00
Rakefile Exposing the rake vendor:clean method to the help message 2014-11-11 06:32:26 +00:00
README.md make sure the coveralls badge is the master one 2015-01-27 14:32:20 +00:00
require-analyze.rb - hacky script to analyze the DEBUG=require csv output grouped by 2013-12-07 12:13:04 -08:00
STYLE.md - clean up style guide a bit 2013-01-03 17:23:36 -08:00

Logstash Code Climate Coverage Status

Logstash is a tool for managing events and logs. You can use it to collect logs, parse them, and store them for later use (like, for searching). Speaking of searching, Logstash comes with a web interface for searching and drilling into all of your logs.

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.

For more info, see http://logstash.net/

Logstash Plugins

AKA "Where'd that plugin go??"

Since version 1.5.0 beta1 (and current master) of Logstash, all plugins have been separated into their own repositories under the logstash-plugins github organization. Each plugin is now a self-contained Ruby gem which gets published to RubyGems.org. Logstash has added plugin infrastructure to easily maintain the lifecyle of the plugin. For more details and rationale behind these changes, see our blogpost.

Elasticsearch logstash-contrib repo is deprecated. We have moved all of the plugins that existed there into their own repositories. We are migrating all of the pull requests and issues from logstash-contrib to the new repositories.

For more info on developing and testing these plugins, please see the README on any plugin repository.

Plugin Issues and Pull Requests

We are migrating all of the existing pull requests to their respective repositories. Rest assured, we will maintain all of the git history for these 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.

Need Help?

Need help? Try #logstash on freenode irc or the logstash-users@googlegroups.com mailing list.

You can also find documentation on the http://logstash.net site.

Developing

To get started, you'll need any ruby available and it should come with the rake tool.

Here's how to get started with Logstash development:

rake bootstrap

Other commands:

# to use Logstash gems or libraries in irb, use the following
# this gets you an 'irb' shell with Logstash's environment
bin/logstash irb

# Run Logstash
bin/logstash agent [options]

Notes about using other rubies. If you don't use rvm, you can probably skip this paragraph. Logstash works with other rubies, and if you wish to use your own ruby you must set USE_RUBY=1 in your environment.

We recommend using flatland/drip for faster startup times during development. To tell Logstash to use drip, set USE_DRIP=1 in your environment.

Testing

There are a few ways to run the tests. For development, using bin/logstash rspec <some spec> will suffice:

% bin/logstash rspec spec/core/timestamp_spec.rb
Using Accessor#strict_set for spec
.............
13 examples, 0 failures
Randomized with seed 8026

If you want to run all the tests from source, do:

rake test

Building

Building is not required. You are highly recommended to download the releases we provide from the Logstash site!

If you want to build the release tarball yourself, run:

rake artifact:tar

You can build rpms and debs, if you need those. Building rpms requires you have fpm, then do this:

# Build an RPM
rake artifact:rpm

# Build a Debian/Ubuntu package
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.