Skip to content

Check your folder and file counts of a path to Elasticsearch with FileCountBeat. (Sample Project)

License

Notifications You must be signed in to change notification settings

hkulekci/filecountbeat

Repository files navigation

Filecountbeat

Welcome to Filecountbeat.

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

Getting Started with Filecountbeat

Requirements

Init Project

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

git remote set-url origin https://github.com/hkulekci/filecountbeat
git push origin master

For further development, check out the beat developer guide.

Build

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

make

Run

To run Filecountbeat with debugging output enabled, run:

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

Test

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

make update

Cleanup

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

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

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.

About

Check your folder and file counts of a path to Elasticsearch with FileCountBeat. (Sample Project)

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published