Install Netdata on Windows | Installation | Learn Netdata
Skip to main content Netdata provides a simple Windows installer for quick setup. Supported Windows Versions and Requirements The Netdata Windows Agent is a 64-bit (x64) application. We recommend Windows 10 / 11 or Windows Server 2019 or newer as the supported baseline. The installer is built to run on older 64-bit Windows editions as far back as Windows Vista and Windows Server 2008, but those versions are not tested or officially supported, and several have reached end-of-life. note Older Windows and Windows Server releases are end-of-life and are more likely to encounter the download/TLS limitations described below.
For the oldest versions, see Will it run on Windows Server 2008? . Requirements 64-bit (x64) Windows. The installer ships only as netdata-x64.msi . Administrator rights. Installation and the running service require elevated (Administrator) privileges. Network access for download. Access and Limitations The local dashboard at http://localhost:19999 works on Windows as it does on Linux, on every plan, including the free Community tier.
Sensitive Functions and the node limit follow the same rules on every operating system; see Access Control and Feature Availability . Download the Windows Installer (MSI) Choose the version that suits your needs: Version Download Link Recommended For Stable Download Stable Most users — stable, well-tested Nightly Download Nightly Users who need the latest features and can handle potential bugs Silent Installation (Command Line) warning Silent installation isn’t supported on Windows Server versions earlier than 2019 when the workflow depends on downloading the installer over TLS.
Use the GUI installer instead. Use silent mode to deploy Netdata without user interaction. Run the command prompt as Administrator. Installation Command Options Option Description /qn Enables silent mode (no user interaction) /i Specifies the path to the MSI installer TOKEN= Claim token from your Netdata Cloud Space ROOMS= (Optional) Comma-separated Room IDs for your node PROXY= (Optional) Proxy address if required INSECURE=1 (Optional) Allow insecure connections (hostname verification disabled) REINSTALL=ALL (Optional) It forces a complete reinstallation of all Netdata components.
TOKEN= is the only option required to connect the Agent to your Space. When you omit ROOMS= , the node is added to your Space and appears under All nodes ; you can move it into Rooms later from the Netdata Cloud UI. Example Command Install Netdata and connect to your Cloud Space: msiexec /qn /i netdata-x64.msi TOKEN="<YOUR_TOKEN>" ROOMS="<YOUR_ROOMS>" Replace: <YOUR_TOKEN> with your claim token <YOUR_ROOMS> with your Room ID(s) To connect the node without assigning it to specific Rooms, pass the token alone: msiexec /qn /i netdata-x64.msi TOKEN="<YOUR_TOKEN>" Download & Install in One Command (PowerShell) $ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest https://github.com/netdata/netdata/releases/latest/download/netdata-x64.msi -OutFile "netdata-x64.msi"; msiexec /qn /i netdata-x64.msi TOKEN=<YOUR_TOKEN> ROOMS=<YOUR_ROOMS> Graphical Installation (GUI) Download the .msi installer.
Double-click to run it. Grant Administrator privileges when prompted. Complete the setup wizard. Claim dialog (GUI installer) During the wizard you'll see a Connect to the Cloud dialog. These fields register the Windows Agent with your Netdata Cloud Space — they are the GUI equivalent of the silent-install TOKEN , ROOMS , PROXY , and INSECURE options. Field What it's for Claim Token The claim token from your Netdata Cloud Space.
This is the only required field. Rooms ID(s) (Optional) The Room(s) you want to add this Agent to. Leave empty to use All nodes . Proxy URL (Optional) A proxy address, if your network requires one to reach Netdata Cloud. Cloud URL The Netdata Cloud endpoint. Defaults to https://app.netdata.cloud . Insecure (Optional) Disables TLS hostname verification when the Agent contacts the Netdata Cloud endpoint. The Claim dialog connects to Netdata Cloud only The Cloud URL and Insecure fields connect the Agent to Netdata Cloud .
They cannot be used to connect this Agent to another local or on-premises Netdata node. If your goal is to stream metrics to a Parent on your local network, entering a local address such as http://192.168.0.x:19999 as the Cloud URL and checking Insecure will not set up streaming. The local dashboard at http://localhost:19999 is this Agent's own web UI — it is not something you connect to through this dialog. To stream to a local Parent, configure stream.conf on the Child instead.
The streaming destination uses Netdata's streaming protocol, not an http:// URL: [stream] enabled = yes destination = PARENT_IP:19999 See the Parent-Child Configuration Reference for the full setup, and the Streaming Routing Reference for routing options. Where the claim settings are stored The values you enter in the claim dialog (or pass to msiexec ) are written to: C:\Program Files\Netdata\etc\netdata\claim.conf The Agent reads this file on startup and connects to your Space.
After a successful connection it also records the resulting identity in C:\Program Files\Netdata\var\lib\netdata\cloud.d\cloud.conf . Connect a node that was installed without a token If the Agent is installed but not connected — no claim.conf exists, or it was installed without a token — you don't need to uninstall or reboot. Create the file yourself and restart the service. Open Notepad as Administrator . Create C:\Program Files\Netdata\etc\netdata\claim.conf with this content, replacing <YOUR_TOKEN> with your claim token: [global] url = https://app.netdata.cloud token = <YOUR_TOKEN> # rooms = # proxy = insecure = no Set rooms to a comma-separated list of Room IDs if you want the node placed in specific Rooms, and set proxy if your network requires one to reach Netdata Cloud.
Both lines are optional — leave them commented out to connect with defaults. Restart the Agent from an Administrator PowerShell prompt: Restart-Service Netdata The node should appear in your Space within a few seconds. If it does not, the Agent reports the claiming result to the Windows Event Log — a rejected or expired token is reported there: Get-WinEvent -LogName 'Netdata/Daemon' -MaxEvents 50 | Where-Object { $_.Message -match 'CLAIM' } Offline (Air-gapped) Installation Use this method to install Netdata on a Windows system with no internet access.
Step 1: Download the MSI On an internet-connected machine, download the MSI installer using one of the links from the Download the Windows Installer table above. Step 2: Transfer to the Offline System Copy the downloaded .msi file to the offline Windows system using a USB drive, network share, or other secure transfer method. Step 3: Install Without Cloud Parameters Open a command prompt as Administrator and run a silent install without TOKEN or ROOMS parameters: msiexec /qn /i netdata-x64.msi note This offline method uses msiexec /qn with a locally available MSI.
On Windows Server versions earlier than 2019, the automated download commands in this document may fail due to TLS compatibility issues, so download the MSI on another machine first or use the GUI installer . Verify the Installation After installation, verify that the Netdata service is running: Get-Service netdata Open http://localhost:19999 to access the Netdata Dashboard. See Access and Limitations for when the local dashboard is available.
License Information By using silent installation, you agree to: GPL-3 License — Netdata Agent NCUL1 License — Netdata Web Interface Where is Netdata? When Netdata is installed on Windows, it automatically registers as a Windows Service and appears in Add or remove programs (also known as Programs and Features or Apps & features in newer Windows versions). To start, stop, or restart the service, use the PowerShell commands described in Service Control .
Automatic
The rest of this page is on the live site.