APEX Beater for Elasticsearch - connecting Java Applications
Go Makefile Python
Switch branches/tags
Nothing to show
Clone or download
Latest commit 5b8d08d Feb 6, 2017
Failed to load latest commit information.
_meta initial Jan 8, 2017
beater cleanup Jan 10, 2017
config port configuration Jan 10, 2017
docs linked docs Jan 16, 2017
tests/system initial Jan 8, 2017
.gitignore initial Jan 8, 2017
.travis.yml initial Jan 8, 2017
CONTRIBUTING.md initial Jan 8, 2017
LICENSE initial Jan 8, 2017
Makefile initial Jan 8, 2017
README.md docs Feb 6, 2017
apexbeat.full.yml port configuration Jan 16, 2017
apexbeat.template-es2x.json initial Jan 8, 2017
apexbeat.template.json initial Jan 8, 2017
apexbeat.yml port configuration Jan 16, 2017
main.go initial Jan 8, 2017
main_test.go initial Jan 8, 2017
vio-apex-isometric5.svg added svg for docs Feb 6, 2017



Welcome to Apexbeat.

APEX extracts contextual data and metrics directly from your Java application.

It helps getting better visibility and understanding of what is happening in the software products' application layer during runtime. Designed to accelerate application analytics, debugging and monitoring.

apexbeat makes it easy to push your extracted data to an ElasticSearch node.

Apex Toolkit

Visit toolkits.verticle.io for more details on APEX.

Getting Started with Apexbeat

This guide will explain how to build apexbeat on your system.

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


Init Project

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

git remote set-url origin https://github.com/verticle-io/apexbeat
git push origin master

For further development, check out the beat developer guide.


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



To run Apexbeat with debugging output enabled, run:

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


To test Apexbeat, run the following command:

make testsuite


make unit-tests
make system-tests
make integration-tests
make coverage-report

The test coverage is reported in the folder ./build/coverage/


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/apexbeat.template.json and etc/apexbeat.asciidoc

make update


To clean Apexbeat source code, run the following commands:

make fmt
make simplify

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

make clean


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

mkdir -p ${GOPATH}/github.com/verticle-io
cd ${GOPATH}/github.com/verticle-io
git clone https://github.com/verticle-io/apexbeat

For further development, check out the beat developer guide.


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.