Skip to content

Beat for performing queries on an LDAP server periodically

License

Notifications You must be signed in to change notification settings

kwojcicki/ldapbeat

Repository files navigation

Ldapbeat

Welcome to Ldapbeat.

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

Getting Started with Ldapbeat

Requirements

Init Project

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

git remote set-url origin https://github.com/kwojcicki/ldapbeat
git push origin master

For further development, check out the beat developer guide.

Build

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

make

Run

To run Ldapbeat with debugging output enabled, run:

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

Test

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

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

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

Beat for performing queries on an LDAP server periodically

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published