Skip to content

Commit

Permalink
Merge pull request #1 from ruflin/logstash-to-filebeat
Browse files Browse the repository at this point in the history
Logstash to Filebeat implementation
  • Loading branch information
tsg committed Sep 10, 2015
2 parents 13678f4 + 0e33af8 commit a3e3649
Show file tree
Hide file tree
Showing 141 changed files with 28,154 additions and 0 deletions.
17 changes: 17 additions & 0 deletions .editorconfig
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# See: http://editorconfig.org
root = true

[*]
charset = utf-8
end_of_line = lf
insert_final_newline = true
trim_trailing_whitespace = true

# Tab indentation (no size specified)
[Makefile]
indent_style = tab

# Matches the exact files either package.json or .travis.yml
[*.yml]
indent_style = space
indent_size = 2
8 changes: 8 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
.idea
filebeat
.DS_Store
.filebeat

cover
profile.cov
filebeat.test
29 changes: 29 additions & 0 deletions .travis.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
language: go

go:
- 1.5

sudo: false

before_install:
# Redo the travis setup but with the elastic/filebeat path. This is needed so the package path is correct
- mkdir -p $HOME/gopath/src/github.com/elastic/filebeat
- rsync -az ${TRAVIS_BUILD_DIR}/ $HOME/gopath/src/github.com/elastic/filebeat/
- export TRAVIS_BUILD_DIR=$HOME/gopath/src/github.com/elastic/filebeat
- cd $HOME/gopath/src/github.com/elastic/filebeat

install:
- make

script:
- make check
- make cover

notifications:
email:
- ruflin@elastic.co

after_success:
# Copy profile.cov to coverage.txt because codecov.io requires this file
- cp profile.cov coverage.txt
- bash <(curl -s https://codecov.io/bash)
65 changes: 65 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,65 @@
# Contributing to logstash-forwarder

All contributions are welcome: ideas, patches, documentation, bug reports,
complaints, etc!

Programming is not a required skill, and there are many ways to help out!
It is more important to us that you are able to contribute.

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

## Want to learn?

Want to lurk about and see what others are doing with logstash and lumberjack?

* The irc channel (#logstash on irc.freenode.org) is a good place for this
* The [mailing list](http://groups.google.com/group/logstash-users) is also
great for learning from others.

## Got Questions?

Have a problem or a question?

* You can email the [mailing list](http://groups.google.com/group/logstash-users)
* alternately, you are welcome to join the IRC channel #logstash on
irc.freenode.org and ask for help there!

## Have an Idea or Feature Request?

* File a ticket on [github](https://github.com/elasticsearch/logstash-forwarder), or email the
[mailing list](http://groups.google.com/group/logstash-users), or email
me personally (jls@semicomplete.com) if that is more comfortable.

## Something Not Working? Found a Bug?

If you think you found a bug, it probably is a bug.

* File it on [github](https://github.com/elasticsearch/logstash-forwarder)
* or the [mailing list](http://groups.google.com/group/logstash-users).

# Contributing Documentation and Code Changes

If you have a bugfix or new feature that you would like to contribute to
logstash, and you think it will take more than a few minutes to produce the fix
(ie; write code), it is worth discussing the change with the logstash users and
developers first! You can reach us via
[github](https://github.com/elasticsearch/logstash-forwarder), the [mailing
list](http://groups.google.com/group/logstash-users), or via IRC (#logstash on
freenode irc)

## Code and Docs Contribution Steps

1. Test your changes! Run the test suite ('go test' and 'rspec')
2. Please make sure you have signed our [Contributor License
Agreement](http://www.elasticsearch.org/contributor-agreement/). We are not
asking you to assign copyright to us, but to give us the right to distribute
your code without restriction. We ask this of all contributors in order to
assure our users of the origin and continuing existence of the code. You
only need to sign the CLA once.
3. Send a pull request! Push your changes to your fork of the repository and
[submit a pull
request](https://help.github.com/articles/using-pull-requests). In the pull
request, describe what your changes do and mention any open issues related
to the pull request.


64 changes: 64 additions & 0 deletions Godeps/Godeps.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

5 changes: 5 additions & 0 deletions Godeps/Readme

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 2 additions & 0 deletions Godeps/_workspace/.gitignore

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

127 changes: 127 additions & 0 deletions Godeps/_workspace/src/github.com/elastic/libbeat/beat/beat.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading

0 comments on commit a3e3649

Please sign in to comment.