- Notifications
You must be signed in to change notification settings - Fork0
Elastic Beat for consuming logs with Fluentd forward protocol
License
salekseev/fluentbeat
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
Welcome to Fluentbeat.
Ensure that this folder is at the following location:${GOPATH}/github.com/salekseev/fluentbeat
- Golang 1.7
To get running with Fluentbeat and also install thedependencies, run the following command:
make setup
It will create a clean git history for each major step. Note that you can always rewrite the history if you wish before pushing your changes.
To push Fluentbeat in the git repository, run the following commands:
git remote set-url origin https://github.com/salekseev/fluentbeatgit push origin master
For further development, check out thebeat developer guide.
To build the binary for Fluentbeat run the command below. This will generate a binaryin the same directory with the name fluentbeat.
make
To run Fluentbeat with debugging output enabled, run:
./fluentbeat -c fluentbeat.yml -e -d "*"
To test Fluentbeat, run the following command:
make testsuite
alternatively:
make unit-testsmake system-testsmake integration-testsmake coverage-report
The test coverage is reported in the folder./build/coverage/
Each beat has a template for the mapping in elasticsearch and a documentation for the fieldswhich is automatically generated based onetc/fields.yml
.To generate etc/fluentbeat.template.json and etc/fluentbeat.asciidoc
make update
To clean Fluentbeat source code, run the following commands:
make fmtmake simplify
To clean up the build directory and generated artifacts, run:
make clean
To clone Fluentbeat from the git repository, run the following commands:
mkdir -p ${GOPATH}/github.com/salekseev/fluentbeatcd ${GOPATH}/github.com/salekseev/fluentbeatgit clone https://github.com/salekseev/fluentbeat
For further development, check out thebeat developer guide.
The beat frameworks provides tools to crosscompile and package your beat for different platforms. This requiresdocker and vendoring as described above. To build packages of your beat, run the following command:
make package
This will fetch and create all images required for the build process. The hole process to finish can take several minutes.