Install Netdata with kickstart.sh
kickstart.sh is the recommended way of installing Netdata.
This script works on all Linux distributions and macOS environments, by detecting the optimal method of installing Netdata directly to the operating system (it will never install a docker image of Netdata - to run Netdata in a container check Installing with Docker).
If you are installing on macOS, make sure to check the install documentation for macOS before continuing.
If you are unsure whether you want nightly or stable releases, read the installation guide.
To install Netdata, run the following as your normal user:
wget -O /tmp/netdata-kickstart.sh https://my-netdata.io/kickstart.sh && sh /tmp/netdata-kickstart.sh
curl https://my-netdata.io/kickstart.sh > /tmp/netdata-kickstart.sh && sh /tmp/netdata-kickstart.sh
If you plan to also connect the node to Netdata Cloud, make sure to replace
YOUR_CLAIM_TOKENwith the claim token of your space, and
YOUR_ROOM_IDwith the ID of the room you are willing to connect the node to.
Verify script integrity
md5sum to verify the integrity of the
kickstart.sh script you will download using the one-line command above,
run the following:
[ "e72c22b3ff4db284c2f36da726759121" = "$(curl -Ss https://my-netdata.io/kickstart.sh | md5sum | cut -d ' ' -f 1)" ] && echo "OK, VALID" || echo "FAILED, INVALID"
If the script is valid, this command will return
kickstart.sh script does the following after being downloaded and run using
- Determines what platform you are running on.
- Checks for an existing installation, and if found updates that instead of creating a new install.
- Attempts to install Netdata using our official native binary packages.
- If there are no official native binary packages for your system (or installing that way failed), tries to install using a static build of Netdata if one is available.
- If no static build is available, installs required dependencies and then attempts to install by building Netdata locally (by downloading the sources and building them directly).
cron.daily, so your Netdata installation will be updated with new nightly versions, unless you override that with an optional parameter.
- Prints a message whether installation succeeded or failed for QA purposes.
Optional parameters to alter your installation
kickstart.sh script accepts a number of optional parameters to control how the installation process works:
--install-prefixSpecify an installation prefix for local builds (by default, we use a sane prefix based on the type of system).
--old-install-prefixSpecify the custom local build's installation prefix that should be removed.
The script automatically detects if it is running interactively, on a user's terminal, or headless in a CI/CD environment. These are options related to overriding this behavior.
--dont-waitDon’t prompt for anything and assume yes whenever possible, overriding any automatic detection of an interactive run. Use this option when installing Netdata agent with a provisioning tool or in CI/CD.
--interactiveAct as if running interactively, even if automatic detection indicates a run is non-interactive.
By default, the script installs the nightly channel of Netdata, providing you with the most recent Netdata. For production systems where stability is more important than new features, we recommend using the stable channel.
--release-channelSpecify a particular release channel to install from. Currently supported release channels are:
nightly: Installs a nightly build (this is currently the default).
stable: Installs a stable release.
default: Explicitly request whatever the current default is.
--install-versionSpecify the exact version of Netdata to install.
By default the script will prefer native builds when they are available, and then static builds. It will fallback to build from source when all others are not available.
--native-onlyOnly install if native binary packages are available. It fails otherwise.
--static-onlyOnly install if a static build is available. It fails otherwise. When installing a static build, the parameter
--static-install-optionscan provide additional options to pass to the static installer code.
--build-onlyOnly install using a local build. It fails otherwise. When it builds from source, the parameter
--local-build-optionscan be used to give additional build options.
By default the script installs a cron job to automatically update Netdata to the latest version of the release channel used.
--auto-updateEnable automatic updates (this is the default).
--no-updatesDisable automatic updates (not recommended).
Netdata Cloud related options
By default, the kickstart script will provide a Netdata agent installation that can potentially communicate with Netdata Cloud, if of course the Netdata agent is further configured to do so.
--claim-tokenSpecify a unique claiming token associated with your Space in Netdata Cloud to be used to connect to the node after the install. This will enable, connect and claim the Netdata agent, to Netdata Cloud.
--claim-urlSpecify a URL to use when connecting to the cloud. Defaults to
https://app.netdata.cloud. Use this option to change the Netdata Cloud URL to point to your Netdata Cloud installation.
--claim-roomsSpecify a comma-separated list of tokens for each War Room this node should appear in.
--claim-proxySpecify a proxy to use when connecting to the cloud in the form of
http://[user:pass@]host:ipfor an HTTP(S) proxy. See connecting through a proxy for details.
--claim-onlyIf there is an existing install, only try to claim it without attempting to update it. If there is no existing install, install and claim Netdata normally.
--require-cloudOnly install if Netdata Cloud can be enabled.
--disable-cloudFor local builds, don’t build any of the Netdata Cloud code at all. For native packages and static builds, use runtime configuration to disable Netdata Cloud support.
By default, the agent is sending anonymous telemetry data to help us take identify the most common operating systems and the configurations Netdata agents run. We use this information to prioritize our efforts towards what is most commonly used by our community.
--disable-telemetryDisable anonymous statistics.
--reinstallIf there is an existing install, reinstall it instead of trying to update it. If there is not an existing install, install netdata normally.
--reinstall-even-if-unsafeIf there is an existing install, reinstall it instead of trying to update it, even if doing so is known to potentially break things (for example, if we cannot detect what type of installation it is). If there is not an existing install, install Netdata normally.
--reinstall-cleanIf there is an existing install, uninstall it before trying to install Netdata. Fails if there is no existing install.
--uninstallUninstall an existing installation of Netdata. Fails if there is no existing install.
--dry-runShow what the installer would do, but don’t actually do any of it.
--dont-start-itDon’t auto-start the daemon after installing. This parameter is not guaranteed to work.
--override-distroOverride the distro detection logic and assume the system is using a specific Linux distribution and release. Takes a single argument consisting of the values of the
/etc/os-releasefor the desired distribution.
The following options are mutually exclusive and specify special operations other than trying to install Netdata normally or update an existing install:
--repositories-onlyOnly install repository configuration packages instead of doing a full install of Netdata. Automatically sets --native-only.
--prepare-offline-install-sourceInstead of insallling the agent, prepare a directory that can be used to install on another system without needing to download anything. See our offline installation documentation for more info.
Additionally, the following environment variables may be used to further customize how the script runs (most users should not need to use special values for any of these):
TMPDIR: Used to specify where to put temporary files. On most systems, the default we select automatically should be fine. The user running the script needs to both be able to write files to the temporary directory, and run files from that location.
ROOTCMD: Used to specify a command to use to run another command with root privileges if needed. By default we try to use sudo, doas, or pkexec (in that order of preference), but if you need special options for one of those to work, or have a different tool to do the same thing on your system, you can specify it here.
DISABLE_TELEMETRY: If set to a value other than 0, behave as if
We publish official DEB/RPM packages for a number of common Linux distributions as part of our releases and nightly builds. These packages are available for 64-bit x86 systems. Depending on the distribution and release they may also be available for 32-bit x86, ARMv7, and AArch64 systems. If a native package is available, it will be used as the default installation method. This allows you to handle Netdata updates as part of your usual system update procedure.
If you want to enforce the usage of native packages and have the installer return a failure if they are not available,
you can do so by adding
--native-only to the options you pass to the installer.
We publish pre-built static builds of Netdata for Linux systems. Currently, these are published for 64-bit x86, ARMv7,
AArch64, and POWER8+ hardware. These static builds are able to operate in a mostly self-contained manner and only
require a POSIX compliant shell and a supported init system. These static builds install under
you are on a platform which we provide static builds for but do not provide native packages for, a static build
will be used by default for installation.
If you want to enforce the usage of a static build and have the installer return a failure if one is not available,
you can do so by adding
--static-only to the options you pass to the installer.
For systems which do not have available native packages or static builds, we support building Netdata locally on the system it will be installed on. When using this approach, the installer will attempt to install any required dependencies for building Netdata, though this may not always work correctly.
If you want to enforce the usage of a local build (perhaps because you require a custom installation prefix,
which is not supported with native packages or static builds), you can do so by adding
--build-only to the
options you pass to the installer.
Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.