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:
- 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
.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 installation 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.
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 between 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-channeloption. If you set this and
--stable-channel, Netdata will use the local files.
kickstart.sh script accepts additional parameters to automatically connect your node to Netdata
Cloud immediately after installation. Find the
rooms strings by signing in to Netdata
Cloud, then clicking on Connect Nodes in the Spaces management
--claim-token: The unique token associated with your Space in Netdata Cloud.
--claim-rooms: A comma-separated list of tokens for each War Room this node should appear in.
--claim-proxy: Should take the form of
socks5[h]://[user:[email protected]]host:ipfor a SOCKS5 proxy, or
http://[user:[email protected]]host:ipfor an HTTP(S) proxy.See connecting through a proxy for details.
--claim-url: Defaults to
md5sum to verify the integrity 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
Or, skip straight to configuring the Netdata Agent.
Read through Netdata's documentation, which is structured based on actions and solutions, to enable features like health monitoring, alarm notifications, long-term metrics storage, exporting to external databases, and more.