The Netdata Agent installs on offline or air gapped systems with a few additional steps.
By default, the
kickstart-static64.sh download Netdata assets, like the precompiled binary and a
few dependencies, using the system's internet connection, but the Agent installer can also use equivalent files already
present on the local filesystem.
First, download the required files. If you're using
kickstart.sh, you need the Netdata tarball, the checksums, the
go.d plugin binary, and the go.d plugin configuration. If you're using
kickstart-static64.sh, you need only the
Netdata tarball and checksums.
Download the files you need to a system of yours that's connected to the internet. Use the commands below, or visit the latest Netdata release page and latest go.d plugin release page to download the required files manually.
If you're using
kickstart.sh, use the following commands:
If you're using
kickstart-static64.sh, use the following commands:
Move downloaded files to the
/tmp directory on the offline system in whichever way your defined policy allows (if
Now you can run either the
kickstart-static64.sh scripts using the
--local-files option. This
option requires you to specify the location and names of the files you just downloaded.
kickstart-static64.shscripts won't download any Netdata assets from the internet. But, you may still need a connection to install dependencies using your system's package manager. The scripts will warn you if your system doesn't have all the dependencies.
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.