OpsCanary
observabilityprometheusPractitioner

Mastering Linux Host Metrics with Prometheus Node Exporter

4 min read Prometheus DocsApr 28, 2026
Share
PractitionerHands-on experience recommended

Monitoring your Linux hosts is crucial for maintaining system health and performance. The Prometheus Node Exporter provides a straightforward way to expose a wide variety of hardware- and kernel-related metrics, allowing you to keep an eye on everything from CPU usage to memory consumption. This visibility is essential for diagnosing issues before they escalate into outages.

The Node Exporter is a single static binary that you can easily install. Download it from the Prometheus releases page, extract it, and run it. By default, it exposes metrics on port 9100. You can verify that it's working by cURLing the /metrics endpoint. The metrics are prefixed with node_, and include valuable data like node_cpu_seconds_total and node_exporter_build_info. For Prometheus to scrape these metrics, you'll need to configure a few parameters: set the scrape_interval (default is 15 seconds), define a job_name (default is 'node'), and specify the targets (default is ['localhost:9100']).

In production, you should be aware that while the Node Exporter is designed for *nix systems, there is a Windows exporter available for Windows environments. Always ensure you're using the right exporter for your operating system. The current version is 1.10.2, and keeping it updated is essential for security and performance improvements.

Key takeaways

  • Install the Node Exporter by downloading and extracting the tarball from the Prometheus releases page.
  • Verify metrics exposure by cURLing the /metrics endpoint on port 9100.
  • Configure Prometheus with a scrape_interval of 15s and a job_name of 'node' to collect metrics.
  • Remember that Node Exporter metrics are prefixed with node_ for easy identification.
  • Use the Node Exporter for *nix systems; consider the Windows exporter for Windows environments.

Why it matters

In production, effective monitoring can prevent downtime and performance degradation. The Node Exporter provides critical insights that enable proactive management of your Linux hosts.

Code examples

shiki
# NOTE: Replace the URL with one from the above mentioned "downloads" page.# Node Exporter is available for multiple OS targets and architectures.# Downloads are available at:# https://github.com/prometheus/node_exporter/releases/download/v<VERSION>/node_exporter-<VERSION>.<OS>-<ARCH>.tar.gz## <VERSION>, <OS>, and <ARCH> are placeholders:# - <VERSION>: Release version (e.g., 1.10.2)# - <OS>: Operating system (e.g., linux, darwin, freebsd)# - <ARCH>: Architecture (e.g., amd64, arm64, 386)## For this example, we will use Node Exporter version 1.10.2 for a Linux system with amd64 architecture.wget https://github.com/prometheus/node_exporter/releases/download/v1.10.2/node_exporter-1.10.2.linux-amd64.tar.gz
tar xvfz node_exporter-1.10.2.linux-amd64.tar.gz
cd node_exporter-1.10.2.linux-amd64
./node_exporter
shiki
curl http://localhost:9100/metrics
shiki
curl http://localhost:9100/metrics | grep "node_"

When NOT to use this

The official docs don't call out specific anti-patterns here. Use your judgment based on your scale and requirements.

Want the complete reference?

Read official docs

Test what you just learned

Quiz questions written from this article

Take the quiz →

Get the daily digest

One email. 5 articles. Every morning.

No spam. Unsubscribe anytime.