Elastic Beat fetching events & status from Icinga 2
Go to file
Blerim Sheqa 4d119a92a6 Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
_meta Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
beater Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
config Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
docs Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
logs Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
tests/system Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
vendor/github.com/elastic/beats Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
.gitignore Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
.travis.yml Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
CONTRIBUTING.md Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
LICENSE Initial commit 2016-12-02 10:41:29 +01:00
Makefile Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
README.md Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
icingabeat.full.yml Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
icingabeat.template-es2x.json Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
icingabeat.template.json Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
icingabeat.yml Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
main.go Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00
main_test.go Add initial files genereated by cookiecutter 2016-12-02 11:51:44 +01:00

README.md

Icingabeat

Welcome to Icingabeat.

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

Getting Started with Icingabeat

Requirements

Init Project

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

git remote set-url origin https://github.com/icinga/icingabeat
git push origin master

For further development, check out the beat developer guide.

Build

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

make

Run

To run Icingabeat with debugging output enabled, run:

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

Test

To test Icingabeat, 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/icingabeat.template.json and etc/icingabeat.asciidoc

make update

Cleanup

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

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

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.