Skip to content

A beat to monitor whether a service is alive or not with the ELK stack

License

Notifications You must be signed in to change notification settings

Corwind/servicebeat

Repository files navigation

Servicebeat

Welcome to Servicebeat.

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

Getting Started with Servicebeat

Requirements

Init Project

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

git remote set-url origin https://github.com/Corwind/servicebeat
git push origin master

For further development, check out the beat developer guide.

Build

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

make

Run

To run Servicebeat with debugging output enabled, run:

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

Test

To test Servicebeat, 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 Servicebeat source code, run the following command:

make fmt

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

make clean

Clone

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

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

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

A beat to monitor whether a service is alive or not with the ELK stack

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published