# Node Exporter

Node Exporter is an open-source Prometheus exporter that exposes hardware and OS metrics from an Unraid host using the official distroless image, letting you monitor your server in your existing Prometheus setup. It is open source and self-hosted, installable on Kubernetes (Helm) and Unraid.

Canonical page: https://ourlocalhost.com/app/3123/node-exporter

## Description

Node Exporter is an open-source Prometheus exporter that exposes hardware and OS metrics from an Unraid host using the official distroless image, letting you monitor your server in your existing Prometheus setup.

## Platform availability

Available on 2 of 10 platforms: Unraid, Helm.

## Health score

83/100 (Excellent), based on 4 of 5 factors.
- Maintained: 100 (last commit 11 days ago)
- Popular: 83 (13,931 GitHub stars)
- Easy to install: 45 (2 install platforms, install notes, Docker image)
- Security check: 86 (no serious findings, CI, tests, OpenSSF Scorecard 6.4/10)

## Links

- GitHub: https://github.com/prometheus/node_exporter
- Kubernetes (Helm): https://artifacthub.io/packages/helm/bitnami/node-exporter
- Unraid: https://ca.unraid.net/apps/node-exporter-18cc5yw0fc1ccs?q=Node-Exporter
- Official website: https://prometheus.io/
- Documentation: https://prometheus.io/docs/guides/node-exporter/

## Common questions

### What container flags does the official Docker deployment require?

Run it with host network and host PID namespace, bind-mount the host root filesystem read-only at /host, and pass --path.rootfs=/host. Any non-root mount points you want to monitor also need to be bind-mounted into the container.

### What extra Docker permission does the timex collector sometimes need?

Start the container with --cap-add=SYS_TIME. This gives it access to the syscalls required by the timex collector on some systems.

### Which port does node_exporter use by default?

It listens on HTTP port 9100 by default. The --help output lists the other options.

### How do I point node_exporter at custom metric files created by scripts?

Add --collector.textfile.directory=/path/to/folder, replacing the path with your metric directory. Without that flag, node_exporter will not read the metric files placed there.

### If node_exporter is installed via /etc/init.d, should I run the binary directly?

No. Use the start and stop actions from /etc/init.d/node_exporter instead. The script tracks a lockfile to prevent accidentally running two copies at once.

## Alternatives

- Better Stack: AI-driven monitoring platform providing incident management, real-time logs, uptime, traces, error tracking, infrastructure analytics, and…
- Datadog: Datadog Agent is an on-host monitoring agent that collects metrics, logs, and traces from hosts, containers, and Kubernetes clusters and se…
- Grafana Loki: Grafana Loki is an open-source log aggregation system.
- Graylog: Graylog is a centralized log management platform built on open standards for capturing, storing, and analyzing terabytes of machine data in…
- HyperDX: An open source observability platform: Unify session replays, logs, traces, and errors – all without the Datadog price tag.
- InfluxDB: InfluxDB is an open source time series database with no external dependencies.
- Kibana: Kibana is the data visualization layer for querying, analyzing, and managing data stored in Elasticsearch.
- New Relic: Pinpoint and solve performance issues in your Ruby, Java, .NET, PHP and Python apps with real user, application and server monitoring.
- Splunk: Splunk is a self-hosted platform for collecting, indexing, searching, and analyzing log and security data, helping homelabbers and operatio…
- VictoriaMetrics: VictoriaMetrics is a fast, cost-effective, and scalable open-source time-series database that stores long-term monitoring metrics, accepts…
- questdb: QuestDB is an open-source database designed to make time-series lightning fast and easy.

---
Source: Our Local Host (https://ourlocalhost.com/app/3123/node-exporter), the self-hosted and open-source app directory.
