Node exporter for windows

We provide precompiled binaries and Docker images
for most officially maintained Prometheus components. If a component is
not listed here, check the respective repository on Github for further
instructions.

There is also a constantly growing number of independently maintained
exporters listed at Exporters
and integrations.

prometheus

The Prometheus monitoring system and time series database. prometheus/prometheus

alertmanager

Prometheus Alertmanager prometheus/alertmanager

blackbox_exporter

Blackbox prober exporter prometheus/blackbox_exporter

consul_exporter

Exporter for Consul metrics prometheus/consul_exporter

graphite_exporter

Server that accepts metrics via the Graphite protocol and exports them as Prometheus metrics prometheus/graphite_exporter

memcached_exporter

Exports metrics from memcached servers for consumption by Prometheus. prometheus/memcached_exporter

mysqld_exporter

Exporter for MySQL server metrics prometheus/mysqld_exporter

node_exporter

Exporter for machine metrics prometheus/node_exporter

promlens

PromLens – The query builder, analyzer, and explainer for PromQL prometheus/promlens

pushgateway

Push acceptor for ephemeral and batch jobs. prometheus/pushgateway

statsd_exporter

StatsD to Prometheus metrics exporter prometheus/statsd_exporter

Introduction

Window Node exporter is agent that collect and send the window machine hardware utilization metrics to the Prometheus server by using HTTP protocol metric, It used port 9182 by default.

Prerequisites

Up and running Prometheus server, Grafana Server in your machine / network environment or you can use the given link to setup Prometheus and Grafana on ubuntu machine to perform this window machine monitoring.

To install Prometheus – https://www.devopstricks.in/install-prometheus-on-ubuntu-22-04/

To install Grafana – https://www.devopstricks.in/installing-grafana-10-on-ubuntu-22-04-lts/

In this post, We will show you how to install window exporter on window machine to get enable monitoring like CPU, Memory, Disk Space, processes and bandwidth etc.

Step 1: Download Window Exporter Package

We need to download the window exporter package by using given link.

https://github.com/prometheus-community/windows_exporter/releases

You can choose the package as per your architecture.

Картинка с сайта: www.devopstricks.in

Click the download the right package, In my case i am using window 10 Prod 64 bit So then i can download windows_exporter-0.24.0-amd64.msi or windows_exporter-0.24.0-arm64.exe.

While downloading the package we should get pop-up like this, We need to click in Keep button and ignore warning that this time.

Картинка с сайта: www.devopstricks.in

Step 2: Installing Window Exporter

After downloaded the window exporter, We need to run the package and allow the installation.

After installation of window exporter package, We need to check the followings endpoint to get window machine metrics like this.

Expose metric URL – localhost:9182/metrics

Картинка с сайта: www.devopstricks.in

Step 3: Add Firewall Rules

We need to open the port 9182 port in your window machine and your cloud environment in order to fetch window metrics from Prometheus server.

Step 4: Configure Prometheus

We need to add the window machine endpoint to fetch metrics To do that we need to add the followings configure in Prometheus configuration file.

To open Prometheus configuration file.

 sudo vim /etc/prometheus/prometheus.yml

Add the in the last following config.

  - job_name: window
    # If prometheus-node-exporter is installed, grab stats about the local
    # machine by default.
    static_configs:
      - targets: ['Type-Window-IP-Here:9182']

This is my sample configuration file with window exporter.

# Sample config for Prometheus.

global:
  scrape_interval:     15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
  evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
  # scrape_timeout is set to the global default (10s).

  # Attach these labels to any time series or alerts when communicating with
  # external systems (federation, remote storage, Alertmanager).
  external_labels:
      monitor: 'example'

# Alertmanager configuration
alerting:
  alertmanagers:
  - static_configs:
    - targets: ['localhost:9093']

# Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
rule_files:
  # - "first_rules.yml"
  # - "second_rules.yml"

# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
  # The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
  - job_name: 'prometheus'

    # Override the global default and scrape targets from this job every 5 seconds.
    scrape_interval: 5s
    scrape_timeout: 5s

    # metrics_path defaults to '/metrics'
    # scheme defaults to 'http'.

    static_configs:
      - targets: ['localhost:9090']

  - job_name: node
    # If prometheus-node-exporter is installed, grab stats about the local
    # machine by default.
    static_configs:
      - targets: ['localhost:9100']
  - job_name: window
    # If prometheus-node-exporter is installed, grab stats about the local
    # machine by default.
    static_configs:
      - targets: ['100.100.100.00:9182']

Save and exit from the vim text editor.

Step 5: Restart Prometheus Service

To get updated and new changes with Prometheus config file, We need to restart the Prometheus service.

To restart.

sudo systemctl restart prometheus.service

To check status.

sudo systemctl status prometheus.service

We are all good to here, Now we need to validate the window target metrics in Prometheus UI.

Step 6: Validate the Window Exporter with Prometheus

To validate the window exporter endpoint with Prometheus to know window Machin’s metric is showing with Prometheus or not.

Access to Prometheus endpoints with http://Prometheus-IP:9090

Click on status > targets

We should get output like this.

Картинка с сайта: www.devopstricks.in

Here we can see that 1 window machine is showing that we just configured, Now we are good to use Grafana.

Step 7: Importing Window Node Exporter Grafana Dashboard

We use the following links to get predefine Window Node Exporter Grafana dashboard.

https://grafana.com/grafana/dashboards/14451-windows-exporter-for-prometheus-dashboard-en/ (Recommended )

https://grafana.com/grafana/dashboards/15620-windows-node-exporter/

https://grafana.com/grafana/dashboards/14694-windows-exporter-dashboard/

https://grafana.com/grafana/dashboards/18699-windows-node-exporter-full-1/

https://grafana.com/grafana/dashboards/14499-windows-node/

https://grafana.com/grafana/dashboards/14510-windows-exporter-node/

https://grafana.com/grafana/dashboards/6593-windows-node/

Картинка с сайта: www.devopstricks.in

Conclusion

We have done successfully enabled window machine monitoring by using window node exporter, Still you are having any issue, So please leave a comment below.

Tutorial for Setting Up Prometheus Node Exporter on Windows with Docker

This tutorial will guide you through setting up the Prometheus Node Exporter on a Windows system using Docker. We will go through the steps to download the image, run the container, and configure the Node Exporter to collect metrics.

Prerequisites

• Docker installed on your Windows system
• Basic knowledge of Docker and containerization
• A Linux environment (e.g., Ubuntu) installed on your Windows system for the Node Exporter to run

1. Download the Prometheus Node Exporter Docker image

First, download the Docker image for the Prometheus Node Exporter from the official Docker Hub repository:

docker pull quay.io/prometheus/node-exporter:latest

2. Run the Docker container

Create a new directory to store the Docker files and logs:

mkdir docker-node-exporter

Move the downloaded Docker image to the new directory:

mv node-exporter_latest.tar.gz docker-node-exporter/

Then, run the Docker container using the following command:

docker run -d --net="host" --pid="host" -v "/:/host:ro,rslave" quay.io/prometheus/node-exporter:latest --path.rootfs=/host

This command will download the image, create a new container, and run the Node Exporter. The --path.rootfs=/host flag mounts the root filesystem of the container to the host system.

Configuration

To configure the Node Exporter to collect metrics, you need to edit the configuration file. Open the node_exporter.yml file in a text editor and add the following configuration:

global:
  scrape_interval: 15s
  evaluation_interval: 15s

scrape_configs:
  - job_name: 'prometheus'
    kubernetes_sd_configs:
      - role: pod

    relabel_configs:
      - source_labels: [__meta_kubernetes_pod_label_app_name]
        action: keep
        regex: prometheus

      - source_labels: [__address__]
        action: replace
        target_label: __address__

This configuration will scrape metrics from the Kubernetes pods labeled with app_name: prometheus and replace the __address__ label with the pod’s IP address.

Troubleshooting

If you encounter the error docker: Error response from daemon: path / is mounted on / but it is not a shared or slave mount, it means that the container is trying to mount a local path that is not a shared or slave mount.

To resolve this issue, make sure that the Docker host has the necessary permissions to access the local path. You can try running the container with the --privileged flag:

docker run -d --net="host" --pid="host" -v "/:/host:ro,rslave" --privileged quay.io/prometheus/node-exporter:latest --path.rootfs=/host

This command will run the container with elevated privileges, allowing it to access the local path.

Conclusion

In this tutorial, you have learned how to set up the Prometheus Node Exporter on a Windows system using Docker. You have downloaded the Docker image, run the container, and configured the Node Exporter to collect metrics. If you encounter any issues, refer to the troubleshooting section for solutions.