It has always had some serious issues that mean it’s not production quality, not to mention the issues inherent in trying to use WSL for production workloads. For Netdata v2.0 and newer, the running natively on Windows is the only officially supported method for monitoring Windows hosts. For versions prior to v2.0, the officially supported method for monitoring Windows hosts is to install the agent on a properly supported platform (which notably does not include WSL) and monitor the Windows host remotely via the Windows Exporter collector as outlined at https://learn.netdata.cloud/docs/collecting-metrics/windows-systems/windows.
ALL support requests regarding this installer will be be closed with reference to the officially supported monitoring methods for Windows hosts.
Netdata installer for Windows using WSL. Use this installer to quickly explore how Netdata monitors Windows hosts.
For production use, you will need to install Netdata on a Linux host.
On your Windows machine:
- Download the latest netdata.msi
- Open an admin CMD terminal (not Powershell) and run
msiexec -i [PATH TO MSI]\netdata.msi [OPTIONS]
⚠️ Running directly the MSI will cause installation to fail. Only install viamsiexec.
⚠️ You will need to reboot your server in order to finish the installation and a user needs to log in, after the reboot, due to microsoft/WSL#2979.
The MSI installer includes and installs automatically the following dependencies:
If WSL2 can't be used, WSL1 will be used instead.
The MSI file is self-contained. Run it to setup the Netdata agent.
The installer will register the WSL distribution called "Netdata", start the agent and add a startup item for the current user.
The agent can be added to Netdata Cloud by running the following as an administrator:
msiexec.exe /i C:\PATH-TO-MSI\netdata.msi TOKEN=[Claim token] ROOMS=[Room IDs] URL=https://app.netdata.cloud
You take the values of [token] and [rooms] from Netdata Cloud. e.g.
To disable telemetry add the binary argument TELEMETRY=0:
msiexec.exe /i C:\PATH-TO-MSI\netdata.msi TELEMETRY=0
The installation log can be found at C:\NETDATA.LOG
To enable an automatic restart, use binary argument AUTORESTART=1:
msiexec.exe /i C:\PATH-TO-MSI\netdata.msi AUTORESTART=1
To specify the WSL version to be used use integer argument WSL=1:
msiexec.exe /i C:\PATH-TO-MSI\netdata.msi WSL=1
For a single instance, you can bring up the linux prompt via wsl -d Netdata, then cd /etc/netdata and use ./edit-config.
For an infrastructure-wide deployment use your preferred deployment tool and do the following:
-
Put all your custom netdata configs under a directory in the target machine (e.g. under c:Users/Public/custom-netdata-config-file-directory)
-
Copy the config files
wsl -d Netdata cp -a /mnt/c/Users/Public/custom-netdata-config-file-directory/ /etc/netdata
- Restart netdata
restart-netdata
- Start netdata
start-netdata
- Stop netdata
stop-netdata
- Restart netdata
restart-netdata
Uninstallation from the Control Panel (Add or remove programs) removes the WSL distro, including the netdata configuration files. The name of the program is "NetdataWSL".
The WXS file will build the MSI file through the WiX toolset.
docker_image_to_wsl_tar will generate the netdata.tar file containing the WSL distro using the public Netdata/netdata Docker image and used by WiX.
![@dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=64&v=4){kind=small}