This page covers detailed instructions on using and configuring the installation script named
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:
This script installs Netdata at
kickstart.sh script does the following after being downloaded and run:
- Detects the Linux distribution and installs the required system packages for building Netdata. Unless you added
--dont-waitoption, it will ask for your permission first.
- Downloads the latest Netdata binary from the binary-packages
repository. You can also run any of these
.runfiles with makeself.
- Installs Netdata by running
./netdata-installer.shfrom the source tree, including any options you might have added.
cron.dailyto enable automatic updates, unless you added the
- 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.
Optional parameters to alter your installation
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.
--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-channeloption. If you set this and
--stable-channel, Netdata will use the local files.
Verify script integrity
md5sum to verify the intregity of the
kickstart-static64.sh script you will download using the one-line
command above, run the following:
If the script is valid, this command will return
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.