windows

Windows machine monitoring with Netdata

This module will monitor one or more Windows machines, using the windows_exporter.

The module collects metrics from the following collectors:

• cpu
• iis
• memory
• net
• logical_disk
• os
• system
• logon
• tcp
• thermalzone
• process
• service
• mssql
• ad
• adcs
• adfs
• netframework_clrexceptions
• netframework_clrinterop
• netframework_clrjit
• netframework_clrloading
• netframework_clrlocksandthreads
• netframework_clrmemory
• netframework_clrremoting
• exchange

Requirements

Netdata monitors Windows hosts by utilizing the Prometheus exporter for Windows machines, a native Windows agent running on each host.

To quickly test Netdata directly on a Windows machine, you can use the Netdata MSI installer. The installer runs Netdata in a custom WSL deployment. WSL was not designed for production environments, so we do not recommend using the installer in production.

For production use, you need to install Netdata on one or more nodes running Linux:

• Install the latest Prometheus exporter for Windows on every Windows host you want to monitor.
• Get the installation commands from Netdata Cloud and install Netdata on one or more Linux nodes.
• Configure each Netdata instance to collect data remotely, from several Windows hosts. Just add one job for each host to windows.conf, as shown in the configuration section.
• [Optional] Disable all plugins except for go.d in netdata.conf, so that you only see Windows metrics.
• [Optional] Set up replication, for high availability.

Automated charts and alerts for your entire Windows infrastructure will be automatically generated. Each Windows host (data collection job) will be identifiable as an "instance" in the Netdata Cloud charts.

Windows Exporter Options

Some windows_exporter collectors are disabled by default. To enable a specific collector, pass its name as an argument to the --collectors.enabled option. See examples.

Metrics

All metrics have prefix.

Labels per scope:

• global: no labels.
• logical disk: disk.
• network device: nic.
• thermalzone: thermalzone.
• website: website.
• mssql instance: mssql_instance.
• database: mssql_instance, database.
• certificate template: cert_template.
• service: service.
• process: process.

Configuration

Edit the go.d/windows.conf configuration file using edit-config from the Netdata config directory, which is typically at /etc/netdata.

cd /etc/netdata # Replace this path with your Netdata config directory
sudo ./edit-config go.d/windows.conf

Needs only url to windows_exporter metrics endpoint. Here is an example for 2 instances:

jobs:
  - name: win_server1
    url: http://203.0.113.10:9182/metrics

  - name: win_server2
    url: http://203.0.113.11:9182/metrics

Hint: Use friendly server names for job names, as these will appear as "instances" in Netdata Cloud charts and on the right side menu of the agent UI charts.

For all available options please see module configuration file.

Troubleshooting

To troubleshoot issues with the windows collector, run the go.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn't working.

• Navigate to the plugins.d directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the plugins setting under [directories].

  cd /usr/libexec/netdata/plugins.d/
  

• Switch to the netdata user.

  sudo -u netdata -s
  

• Run the go.d.plugin to debug the collector:

  ./go.d.plugin -d -m windows