Skip to content
No description, website, or topics provided.
Go Makefile Python Other
Branch: master
Clone or download
mairea50
mairea50 hange field name dedup.ratio to dedup_ratio
Logstash could not parse field name dedup.ratio becasuse of this field
Latest commit 2569534 Mar 26, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
_meta Add generated zfsbeat files Feb 13, 2019
beater hange field name dedup.ratio to dedup_ratio Mar 26, 2019
cmd
config hange field name dedup.ratio to dedup_ratio Mar 26, 2019
data First try Mar 6, 2019
docs Add generated zfsbeat files Feb 13, 2019
include Add generated zfsbeat files Feb 13, 2019
tests/system Add generated zfsbeat files Feb 13, 2019
vendor/github.com Update .go-version Mar 8, 2019
.dockerignore Add init Dockerfile and travis Mar 6, 2019
.editorconfig Add generated zfsbeat files Feb 13, 2019
.gitignore Add generated zfsbeat files Feb 13, 2019
.gitlab-ci.yml Add init Dockerfile and travis Mar 6, 2019
.travis.yml Update go version Mar 8, 2019
CONTRIBUTING.md Add generated zfsbeat files Feb 13, 2019
Dockerfile Add init Dockerfile and travis Mar 6, 2019
LICENSE.txt Add generated zfsbeat files Feb 13, 2019
Makefile Update Makefile Mar 8, 2019
NOTICE.txt Add generated zfsbeat files Feb 13, 2019
README.md Add generated zfsbeat files Feb 13, 2019
fields.yml Add generated zfsbeat files Feb 13, 2019
magefile.go Add generated zfsbeat files Feb 13, 2019
main.go Add generated zfsbeat files Feb 13, 2019
main_test.go Add generated zfsbeat files Feb 13, 2019
make.bat Add generated zfsbeat files Feb 13, 2019
zfsbeat.docker.yml Add generated zfsbeat files Feb 13, 2019
zfsbeat.reference.yml Add generated zfsbeat files Feb 13, 2019
zfsbeat.yml hange field name dedup.ratio to dedup_ratio Mar 26, 2019

README.md

Zfsbeat

Welcome to Zfsbeat.

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

Getting Started with Zfsbeat

Requirements

Init Project

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

git remote set-url origin https://github.com/maireanu/zfsbeat
git push origin master

For further development, check out the beat developer guide.

Build

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

make

Run

To run Zfsbeat with debugging output enabled, run:

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

Test

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

make fmt

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

make clean

Clone

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

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

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.

You can’t perform that action at this time.