command module
Version: v0.0.0-...-e75ec8f Latest Latest

This package is not in the latest version of its module.

Go to latest
Published: Oct 17, 2017 License: Apache-2.0 Imports: 3 Imported by: 0



Build Status

Welcome to Krakenbeat.

Ensure that this folder is at the following location: ${GOPATH}/

Getting Started with Krakenbeat

Selection pair to watch
  1. Use the Kraken API to check tradeable pair
  2. Insert the selected pairs in the krakenbeat.yml file
  3. That's all
Using Docker
  1. Clone
  2. set your krakenbeat.yml
  3. docker build -t krakenbeat .
  4. docker run --name krakenbeat --network=host --restart=always --log-opt max-size=10m -d krakenbeat

Follow for no-docker method

Init Project

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

git remote set-url origin
git push origin master

For further development, check out the beat developer guide.


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


To run Krakenbeat with debugging output enabled, run:

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

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

make update

To clean Krakenbeat source code, run the following commands:

make fmt
make simplify

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

make clean

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

mkdir -p ${GOPATH}/
cd ${GOPATH}/
git clone

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.


The Go Gopher

There is no documentation for this package.

Source Files


Path Synopsis

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL