ignitebeat

command module
v0.0.0-...-6e1f017 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Sep 7, 2018 License: Apache-2.0, Apache-2.0 Imports: 3 Imported by: 0

README

Ignitebeat

Welcome to Ignitebeat.

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

Getting Started with Ignitebeat

Requirements
Init Project

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

git remote set-url origin https://github.com/shreychen/ignitebeat
git push origin master

For further development, check out the beat developer guide.

Build

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

make
Run

To run Ignitebeat with debugging output enabled, run:

./ignitebeat -c ignitebeat.yml -e -d "*"
Test

To test Ignitebeat, 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 Ignitebeat 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 Ignitebeat from the git repository, run the following commands:

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

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 whole process to finish can take several minutes.

Documentation

The Go Gopher

There is no documentation for this package.

Directories

Path Synopsis

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL