Node Exporter systemd

Running node_exporter directly with ./node_exporter is fine for quick tests, but it has two limitations: it runs in the foreground and it won’t start automatically after a reboot. To let systemd manage node_exporter — so you can use systemctl start node_exporter, systemctl status node_exporter, and have it start on boot — create a system user, place the binary in a standard location, and provide a systemd service unit. Quick local vs systemd commands:

# Quick local test (runs in foreground)
./node_exporter

# Systemd managed (daemonized, can enable on boot)
sudo systemctl start node_exporter

These steps assume you have already downloaded and extracted the node_exporter tarball and are in the extracted directory.

Below are concise, ordered steps to install and configure node_exporter under systemd, with explanations and tips.

1. Move the binary, create a system user, set ownership

Copy the binary to a standard location, create a non-privileged system user, and set ownership so the service runs with least privilege.

sudo cp node_exporter /usr/local/bin/
sudo useradd --no-create-home --shell /sbin/nologin --system node_exporter
sudo chown node_exporter:node_exporter /usr/local/bin/node_exporter
sudo chmod 0755 /usr/local/bin/node_exporter

Notes:

--no-create-home and --shell /sbin/nologin ensure the account is non-interactive.
chmod 0755 makes the binary executable for the system user.
If you want to run node_exporter on a non-default port or bind to localhost, you can later add flags to the systemd unit’s ExecStart (example shown below).

2. Create the systemd service unit

Create /etc/systemd/system/node_exporter.service with the following content:

[Unit]
Description=Node Exporter
Wants=network-online.target
After=network-online.target

[Service]
User=node_exporter
Group=node_exporter
Type=simple
ExecStart=/usr/local/bin/node_exporter

[Install]
WantedBy=multi-user.target

Common reasons to adjust the unit:

Add startup flags to ExecStart, for example to bind to localhost:
- ExecStart=/usr/local/bin/node_exporter --web.listen-address=127.0.0.1:9100
To provide environment variables, use Environment= or an EnvironmentFile=.

Table — key unit directives and purpose

Directive	Purpose	Example / Notes
`User` / `Group`	Run the service as an unprivileged user	`User=node_exporter`
`Wants` / `After`	Ensure network is available before starting	`Wants=network-online.target`
`Type`	How systemd expects the process to behave	`Type=simple` for processes that run in foreground
`ExecStart`	Command to start the service	`/usr/local/bin/node_exporter`

3. Reload systemd, start and enable the service

Reload the systemd manager configuration, start the service immediately, check its status, and enable it so it starts on boot.

sudo systemctl daemon-reload
sudo systemctl start node_exporter
sudo systemctl status node_exporter
sudo systemctl enable node_exporter

Helpful troubleshooting commands:

View logs: sudo journalctl -u node_exporter -f
Check whether the unit file syntax is valid: systemd-analyze verify /etc/systemd/system/node_exporter.service
If you change the unit, re-run sudo systemctl daemon-reload and sudo systemctl restart node_exporter.

Be careful exposing the metrics endpoint publicly. node_exporter does not authenticate requests. If the host is internet-facing, bind node_exporter to 127.0.0.1:9100 or restrict access via firewall rules.

4. Verify metrics are being served

Use curl or a browser to confirm metrics are available on the expected endpoint:

curl http://localhost:9100/metrics

Example (truncated) output returned by the endpoint:

node_vmstat_pswout 0
# HELP process_cpu_seconds_total Total user and system CPU time spent in seconds.
# TYPE process_cpu_seconds_total counter
process_cpu_seconds_total 0
# HELP process_max_fds Maximum number of open file descriptors.
# TYPE process_max_fds gauge
process_max_fds 524288
# HELP process_open_fds Number of open file descriptors.
# TYPE process_open_fds gauge
process_open_fds 9
# HELP process_resident_memory_bytes Resident memory size in bytes.
# TYPE process_resident_memory_bytes gauge
process_resident_memory_bytes 1.2214272e+07
# HELP process_start_time_seconds Start time of the process since unix epoch in seconds.
# TYPE process_start_time_seconds gauge
process_start_time_seconds 1.66831526456e+09
# HELP process_virtual_memory_bytes Virtual memory size in bytes.
# TYPE process_virtual_memory_bytes gauge
process_virtual_memory_bytes 7.42240256e+08
# HELP process_virtual_memory_max_bytes Maximum amount of virtual memory available in bytes.
# TYPE process_virtual_memory_max_bytes gauge
process_virtual_memory_max_bytes 1.8446744073709552e+19
# HELP promhttp_metric_handler_errors_total Total number of internal errors encountered by the promhttp metric handler.
# TYPE promhttp_metric_handler_errors_total counter
promhttp_metric_handler_errors_total{cause="encoding"} 0
promhttp_metric_handler_errors_total{cause="gathering"} 0
# HELP promhttp_metric_handler_requests_in_flight Current number of scrapes being served.
# TYPE promhttp_metric_handler_requests_in_flight gauge
promhttp_metric_handler_requests_in_flight 1
# HELP promhttp_metric_handler_requests_total Total number of scrapes by HTTP status code.
# TYPE promhttp_metric_handler_requests_total counter
promhttp_metric_handler_requests_total{code="200"} 0
promhttp_metric_handler_requests_total{code="500"} 0
promhttp_metric_handler_requests_total{code="503"} 0

To have Prometheus scrape this target, add it to your prometheus.yml scrape configuration (for example, using localhost:9100 if Prometheus runs on the same host). See Prometheus scrape configuration docs: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_configs

Example Prometheus scrape config snippet:

scrape_configs:
  - job_name: 'node_exporter'
    static_configs:
      - targets: ['localhost:9100']

Troubleshooting checklist

Service won’t start: run sudo journalctl -u node_exporter -b --no-pager and inspect the logs.
Port already in use: check ss -ltnp | grep 9100 or adjust --web.listen-address.
Permissions issues: verify file ownership ls -l /usr/local/bin/node_exporter and that User=node_exporter exists.
Unit changes not applied: run sudo systemctl daemon-reload before restart.

Links and references

Prometheus scrape configuration: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_configs
systemd documentation: https://www.freedesktop.org/wiki/Software/systemd/
node_exporter GitHub releases: https://github.com/prometheus/node_exporter/releases

Now node_exporter will be managed by systemd, start automatically on boot when enabled, and expose metrics that Prometheus can scrape.

Introduction

Observability Fundamentals

Prometheus Fundamentals

PromQL

Dashboarding & Visualization

Application Instrumentation

Service Discovery

Push Gateway

Alerting

Monitoring Kubernetes

Conclusion

Scaling & Long Term Storage

Node Exporter systemd

1. Move the binary, create a system user, set ownership

2. Create the systemd service unit

3. Reload systemd, start and enable the service

4. Verify metrics are being served

Troubleshooting checklist

Links and references

Watch Video

​1. Move the binary, create a system user, set ownership

​2. Create the systemd service unit

​3. Reload systemd, start and enable the service

​4. Verify metrics are being served

​Troubleshooting checklist

​Links and references

Watch Video

1. Move the binary, create a system user, set ownership

2. Create the systemd service unit

3. Reload systemd, start and enable the service

4. Verify metrics are being served

Troubleshooting checklist

Links and references