Skip to content

connexta/ddfbeat

Repository files navigation

DDFbeat

Welcome to DDFbeat.

Ensure that this folder is at the following location: ${GOPATH}/src/github.com/connexta/ddfbeat

Getting Started with DDFbeat

Requirements

Init Project

To get running with DDFbeat 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 DDFbeat in the git repository, run the following commands:

git remote set-url origin https://github.com/connexta/ddfbeat
git push origin master

For further development, check out the beat developer guide.

Configuration Options

This beat can be configured using environment variables. They are as follows:

Environment variable Description
DDFBeat_SSLSkip Set to true to skip SSL certificate verification
DDFBeat_CertPath The path to the ca cert to be used during secure connections

Build

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

make

Run

To run DDFbeat with debugging output enabled, run:

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

Test

To test DDFbeat, 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 fields.yml by running the following command.

make update

Cleanup

To clean DDFbeat source code, run the following command:

make fmt

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

make clean

Clone

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

mkdir -p ${GOPATH}/src/github.com/connexta/ddfbeat
git clone https://github.com/connexta/ddfbeat ${GOPATH}/src/github.com/connexta/ddfbeat

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 release

This will fetch and create all images required for the build process. The whole process to finish can take several minutes.

About

ELK beat for collecting metrics from the DDF metrics endpoint

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published