An Elastic Beats for indexing HackerNews posts
Switch branches/tags
Nothing to show
Clone or download
Ullaakut Improve business logic
Remove error field in story, as it was in the end simply used to log in the parent thread, and moved the logging to the child thread instead.
DRY the storyIDoken by using fmt.Sprintf()
Remove legacy 'busy' boolean value that was used when fetchStories was async
Add comments everywhere
Wrap errors using errors.Wrap() instead of fmt.Errorf()
Make configuration printing more readable
Latest commit e9546a4 Feb 21, 2018


Hackerbeat indexes the top stories of HackerNews into an ElasticSearch instance.

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

Getting Started with Hackerbeat



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



To run Hackerbeat with debugging output enabled, run:

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


To test Hackerbeat, 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 fields.yml by running the following command.

make update


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

make clean


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

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

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.