Beat to upload GPFS related metrics
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
_meta
beater
config
docs
parser
tests/system
.gitignore
.travis.yml
CONTRIBUTING.md
LICENSE
Makefile
README.md
gpfsbeat.template.json
main.go
main_test.go

README.md

Gpfsbeat

Welcome to Gpfsbeat.

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

Getting Started with Gpfsbeat

Requirements

Init Project

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

git remote set-url origin https://github.com/hpcugent/gpfsbeat
git push origin master

For further development, check out the beat developer guide.

Build

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

make

Run

To run Gpfsbeat with debugging output enabled, run:

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

Test

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

make update

Cleanup

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

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

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.