Fluentbeat

Welcome to Fluentbeat - an Elastic Beat for consuming logs with Fluentd forward protocol.

Ensure that this folder is at the following location: ${GOPATH}/github.com/athenahealth/fluentbeat

Getting Started with Fluentbeat

Requirements

• Golang 1.7
• Glide

Init Project

To get running with Fluentbeat and also install the dependencies, 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/athenahealth/fluentbeat
git push origin master

For further development, check out the beat developer guide.

Build

To build the binary for Fluentbeat run the command below. This will generate a binary in the same directory with the name fluentbeat.

make

Run

To run Fluentbeat with debugging output enabled, run:

./fluentbeat -c fluentbeat.yml -e -d "*"

Test

To test Fluentbeat, run the following command:

make testsuite

alternatively:

make unit-tests
make system-tests
make integration-tests
make coverage-report

The test coverage is reported in the folder ./build/coverage/

Update

Each beat has a template for the mapping in elasticsearch and a documentation for the fields which is automatically generated based on etc/fields.yml. To generate etc/fluentbeat.template.json and etc/fluentbeat.asciidoc

make update

Cleanup

To clean Fluentbeat source code, run the following commands:

make fmt
make simplify

To clean up the build directory and generated artifacts, run:

make clean

Clone

To clone Fluentbeat from the git repository, run the following commands:

mkdir -p ${GOPATH}/github.com/athenahealth/fluentbeat
cd ${GOPATH}/github.com/athenahealth/fluentbeat
git clone https://github.com/athenahealth/fluentbeat

For further development, check out the beat developer guide.

Packaging

The beat frameworks provides tools to crosscompile and package your beat for different platforms. This requires docker 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.