Skip to main content

Node Exporter Windows Metrics

This pack helps you monitor your Windows server based on metrics exported by Prometheus exporter.

Pack Assets​


The Centreon Monitoring Connector Node Exporter Windows Metrics brings a host template:

  • App-Monitoring-Node-Exporter-Windows-custom

It brings the following service templates:

Service AliasService TemplateService DescriptionDefaultDiscovery
Node-CpuApp-Monitoring-Node-Exporter-Windows-CpuCheck node CPU usageX
Node-MemoryApp-Monitoring-Node-Exporter-Windows-MemoryCheck node memory usageX
Node-Service-NameApp-Monitoring-Node-Exporter-Windows-Service-NameCheck services stateXX
Node-StorageApp-Monitoring-Node-Exporter-Windows-StorageCheck node storage usageXX
Node-TrafficApp-Monitoring-Node-Exporter-Windows-TrafficCheck network traffic per interfaceXX

Discovery rules​

Rule NameDescription
App-Monitoring-Node-Exporter-Windows-Interface-NameDiscover network interfaces and monitor their usage.
App-Monitoring-Node-Exporter-Windows-Storage-NameDiscover disks and monitor their usage.
App-Monitoring-Node-Exporter-Windows-Service-NameDiscover services and monitor their state.

Collected metrics & status​

Metric NameUnit


This pack is based on community Prometheus exporter for Windows machines:


  1. Install the package on every Centreon poller expected to monitor Windows resources:
yum install centreon-plugin-Applications-Monitoring-Nodeexporter-Windows
  1. On the Centreon web interface, on page Configuration > Monitoring Connector Manager, install the Node Exporter Windows Metrics Centreon Monitoring Connector.



  • Log into Centreon and add a new host through Configuration > Hosts.
  • Fill the Name, Alias & IP Address/DNS fields according to your Windows server settings.
  • Apply the App-Monitoring-Node-Exporter-Windows-custom template to the host.
  • Once the template is applied, fill in the corresponding macros. Some macros are mandatory.
EXTRAOPTIONSAny extra option you may want to add to every command line (eg. a --verbose flag)
NODEEXPORTERURL(Default: '/metrics')

How to check in the CLI that the configuration is OK and what are the main options for?​

Once the plugin is installed, log into your Centreon poller's CLI using the centreon-engine user account (su - centreon-engine) and test the plugin by running the following command:

/usr/lib/centreon/plugins// \
--plugin=apps::monitoring::nodeexporter::windows::plugin \
--mode=services \
--hostname= \
--urlpath='/metrics' \
--port='9182' \
--proto='http' \
--service='' \
--warning-status='' \
--critical-status='%{start_mode} =~ /auto/ && %{status} !~ /^running$/' \

The expected command output is shown below:

CRITICAL: Service : 'winserv1' [state: 'stopped'] [start_mode: 'auto'] - Service : 'sysmonitor' [state: 'stopped'] [start_mode: 'auto']

All available options for a given mode can be displayed by adding the --help parameter to the command:

/usr/lib/centreon/plugins// \
--plugin=apps::monitoring::nodeexporter::windows::plugin \
--mode=services \

All available modes can be displayed by adding the --list-mode parameter to the command:

/usr/lib/centreon/plugins// \
--plugin=apps::monitoring::nodeexporter::windows::plugin \


Please find the troubleshooting documentation for Centreon Plugins typical issues.