Skip to content

Latest commit

 

History

History
79 lines (58 loc) · 4.84 KB

kickstart.md

File metadata and controls

79 lines (58 loc) · 4.84 KB
Raw

Install Netdata with kickstart.sh

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

This method is fully automatic on all Linux distributions. To install Netdata from source, 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.sh)

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

What does kickstart.sh do?

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

  • Detects the Linux distribution and installs the required system packages for building Netdata. Unless you added the --dont-wait option, it will ask for your permission first.
  • Checks for an existing installation, and if found updates that instead of creating a new install.
  • Downloads the latest Netdata source tree to /usr/src/netdata.git.
  • Installs Netdata by running ./netdata-installer.sh from the source tree, using any optional parameters you have specified.
  • Installs netdata-updater.sh to 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

The kickstart.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 install is detected, reinstall instead of trying to update it. Note that this cannot be used to change 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.sh script you will download using the one-line command above, run the following:

[ "8df7a45b2abb336c84507b7c107bcba3" = "$(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 OK, VALID.

What's next?

When you're finished with installation, check out our single-node or infrastructure monitoring quickstart guides based on your use case.

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.

analytics