Logstash - transport and process your logs, events, or other data
Find a file
MikeSchuette cd0e08e29d Fix URIPARAM to allow square brackets
PHP uses these all the time.
2012-11-27 11:55:20 -06:00
bin make bin/logstash a shell script now that we don't use bundler 2012-11-06 18:01:07 -08:00
docs Remove weird unicode spacing 2012-11-13 15:53:07 -08:00
etc Correcting grep config in nagios doc/example 2012-07-10 09:44:02 +02:00
lib - update doc comments 2012-11-27 01:05:42 -08:00
misc - add some pipeline ideas related to the big logstash agent refactor. 2012-05-24 01:17:43 -07:00
patterns Fix URIPARAM to allow square brackets 2012-11-27 11:55:20 -06:00
screencast 2010-11-11 07:37:48 +00:00
spec - add test converting US-ASCII to UTF-8 from generator input to redis 2012-11-22 09:05:00 +00:00
src/net/logstash - variables, use them. 2011-08-22 01:10:09 -07:00
test Merge branch 'master' of github.com:logstash/logstash 2012-10-22 11:44:41 -07:00
.gitignore Added Eclipse project files to .gitignore 2012-11-20 16:28:53 +01:00
.travis.yml Enabled LogStash to be built and tested on the Travis-CI Platform (travis-ci.org) 2012-02-09 13:23:34 -07:00
CHANGELOG - Update changelog based on reading git log v1.1.5..master 2012-11-23 10:21:35 -08:00
CONTRIBUTORS Update name for zuazo 2012-10-29 10:00:52 -07:00
gembag.rb Default to logstash.gemspec 2012-11-16 22:34:07 -08:00
Gemfile - clean out gemfile (Should use only the gemspec now) 2012-08-29 16:44:03 -07:00
LICENSE update copyright years 2011-02-19 11:45:52 -08:00
logstash-event.gemspec fix license 2012-11-07 11:58:10 -08:00
logstash.gemspec - Resurrect the websocket output! 2012-11-27 01:03:00 -08:00
Makefile Add more tests to jartests 2012-11-20 02:20:20 +00:00
pl.rb - start hacking on a new pipeline implementation focusing on 2012-11-02 23:42:07 -07:00
pl2.rb - start hacking on a new pipeline implementation focusing on 2012-11-02 23:42:07 -07:00
README.md Update readme for jruby 1.7.0 and a few other small changes 2012-11-14 09:48:35 -08:00
STYLE.md tune style docs 2012-11-10 19:31:45 -08:00

logstash

Build 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/

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

Building

To work on the code without building a jar, install rvm and run the following:

# Install JRuby with rvm
rvm install jruby-1.7.0
rvm use jruby-1.7.0

# Install logstash dependencies
ruby gembag.rb logstash.gemspec

# Run logstash
bin/logstash agent [options]

jar releases are available here: http://logstash.objects.dreamhost.com/ If you want to build the jar yourself, run:

make jar

rpm, deb, or other package formats are not currently available, but are easy to build with fpm. If you are interested in seeing future releases include your favorite packaging format, please let me know.

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.

That said, some basic guidelines, which you are free to ignore :)

  • Have a problem you want logstash to solve for you? You can email the mailing list, or join the IRC channel #logstash on irc.freenode.org, or email me personally (jls@semicomplete.com)
  • Have an idea or a feature request? File a ticket on jira, or email the mailing list, or email me personally (jls@semicomplete.com) if that is more comfortable.
  • If you think you found a bug, it probably is a bug. File it on jira or send details to the mailing list.
  • If you want to send patches, best way is to fork this repo and send me a pull request. If you don't know git, I also accept diff(1) formatted patches - whatever is most comfortable for you.
    • DO NOT MODIFY Gemfile.lock IN YOUR PULL REQUESTS. THIS WILL CAUSE MERGE FAILURES.
  • Want to lurk about and see what others are doing? IRC (#logstash on irc.freenode.org) is a good place for this as is the mailing list