Install Netdata with kickstart-static64.sh

This page covers detailed instructions on using and configuring the installation script named kickstart-static64.sh.

This method uses a pre-compiled static binary to install Netdata on any Intel/AMD 64bit Linux system and on any Linux distribution, even those with a broken or unsupported package manager.

To install Netdata from a static binary package, including all dependencies required to connect to Netdata Cloud, and get automatic nightly updates, run the following as your normal user:

bash <(curl -Ss https://my-netdata.io/kickstart-static64.sh)

This script installs Netdata at /opt/netdata.

See our installation guide for details about automatic updates or nightly vs. stable releases.

What does kickstart-static64.sh do?

The kickstart.sh script does the following after being downloaded and run:

  • Checks to see if there is an existing installation, and if there is updates that in preference to reinstalling.
  • Downloads the latest Netdata binary from the binary-packages repository. You can also run any of these .run files with makeself.
  • Installs Netdata by running ./netdata-installer.sh from the source tree, including any options you might have added.
  • Installs netdata-updater.sh to cron.daily to enable automatic updates, unless you added the --no-updates option.
  • Prints a message about whether the insallation succeeded for failed for QA purposes.

If your shell fails to handle the above one-liner, you can download and run the kickstart-static64.sh script manually.

# download the script with curl
curl https://my-netdata.io/kickstart-static64.sh >/tmp/kickstart-static64.sh
# or, download the script with wget
wget -O /tmp/kickstart-static64.sh https://my-netdata.io/kickstart-static64.sh
# run the downloaded script (any sh is fine, no need for bash)
sh /tmp/kickstart-static64.sh

Optional parameters to alter your installation

The kickstart-static64.sh script passes all its parameters to netdata-installer.sh, which you can use to customize your installation. Here are a few important parameters:

  • --dont-wait: Enable automated installs by not prompting for permission to install any required packages.
  • --dont-start-it: Prevent the installer from starting Netdata automatically.
  • --stable-channel: Automatically update only on the release of new major versions.
  • --nightly-channel: Automatically update on every new nightly build.
  • --disable-telemetry: Opt-out of anonymous statistics we use to make Netdata better.
  • --no-updates: Prevent automatic updates of any kind.
  • --reinstall: If an existing installation is detected, reinstall instead of attempting to update it. Note that this cannot be used to switch betwen installation types.
  • --local-files: Used for offline installations. Pass four file paths: the Netdata tarball, the checksum file, the go.d plugin tarball, and the go.d plugin config tarball, to force kickstart run the process using those files. This option conflicts with the --stable-channel option. If you set this and --stable-channel, Netdata will use the local files.

Verify script integrity

To use md5sum to verify the intregity of the kickstart-static64.sh script you will download using the one-line command above, run the following:

[ "efddf41d3c19c4988601aecf5b483e3a" = "$(curl -Ss https://my-netdata.io/kickstart-static64.sh | md5sum | cut -d ' ' -f 1)" ] && echo "OK, VALID" || echo "FAILED, INVALID"

If the script is valid, this command will return OK, VALID.

What's next?

When you finish installing Netdata, be sure to visit our step-by-step guide for a fully-guided tour into Netdata's capabilities and how to configure it according to your needs.

Or, if you're a monitoring and system administration pro, skip ahead to our getting started guide for a quick overview.

Last updated on