Skip to content

netdata static binary build

To build the static binary 64-bit distribution package, run:

$ cd /path/to/netdata.git
$ ./packaging/makeself/

The program will:

  1. setup a new docker container with Alpine Linux
  2. install the required alpine packages (the build environment, needed libraries, etc)
  3. download and compile third party apps that are packaged with netdata (bash, curl, etc)
  4. compile netdata

Once finished, a file named will be created in the current directory. This is the netdata binary package that can be run to install netdata on any other computer.

building binaries with debug info

To build netdata binaries with debugging / tracing information in them, use:

$ cd /path/to/netdata.git
$ ./packaging/makeself/ debug

These binaries are not optimized (they are a bit slower), they have certain features disables (like log flood protection), other features enables (like debug flags) and are not stripped (the binary files are bigger, since they now include source code tracing information).

debugging netdata binaries

Once you have installed a binary package with debugging info, you will need to install valgrind and run this command to start netdata:

PATH="/opt/netdata/bin:${PATH}" valgrind --undef-value-errors=no /opt/netdata/bin/srv/netdata -D

The above command, will run netdata under valgrind. While netdata runs under valgrind it will be 10x slower and use a lot more memory.

If netdata crashes, valgrind will print a stack trace of the issue. Open a github issue to let us know.

To stop netdata while it runs under valgrind, press Control-C on the console.

If you omit the parameter --undef-value-errors=no to valgrind, you will get hundreds of errors about conditional jumps that depend on uninitialized values. This is normal. Valgrind has heuristics to prevent it from printing such errors for system libraries, but for the static netdata binary, all the required libraries are built into netdata. So, valgrind cannot appply its heuristics and prints them.