Skip to main content

Node exporter (node-exporter)

Exposes the hardware and operating system metrics of every host (CPU, memory, disks, network, systemd units).

Generated from catalog/services/node-exporter.yaml: do not edit by hand.

Summary​

Version1.9.1
Useinstall and configure
Layerinfrastructure (shown apart)
CategoryObservability
Installation methodsbinary
External connectionno
Sandbox onlyno

Licence​

SPDX identifierApache-2.0
Licence policycore licence (MIT or Apache-2.0)
Licence exception-
Platform componentnode-exporter

Packages and artifacts​

A package the project of the service publishes (its image, its binary archive, its Python or OS package) carries the licence of the service; a third-party package carries the licence written on its row, read from the official upstream metadata.

KindPackageVersionLicenceDetails
binary archivenode_exporter-1.9.1.linux-amd64.tar.gz1.9.1Apache-2.0https://github.com/prometheus/node_exporter/releases/download/v1.9.1/node_exporter-1.9.1.linux-amd64.tar.gz, x86_64, checksum sha256

Supported systems and architectures​

MethodOperating systemsArchitectures
binaryRHEL family (dnf), Debian family (apt), Arch Linux (pacman)x86_64 (architecture of the artifacts of the descriptor)

Certified host systems: RHEL 8/9/10, Rocky Linux 8/9/10, AlmaLinux 8/9/10, Oracle Linux 8/9, CentOS Stream 9/10, Ubuntu 22.04/24.04, Debian 12, Arch Linux (rolling). The host preflight accepts these systems (other releases of a known family give a warning, end of life releases are refused) and the x86_64 and aarch64 architectures.

Prerequisites​

Host​

The descriptor declares no host preflight check.

Network and ports​

ComponentPort namePortOpened in the host firewall
node-exportermetrics9100/tcpyes

Services and connections needed​

This service has no dependency.

Installation methods and modes​

MethodDefaultWhat the method uses
binaryyesthe binary archives of the descriptor, unpacked under the service directory

Components​

ComponentKindInstallation methodsPorts
Node exporter (node-exporter)workerbinary9100/tcp

Every host (every-host) (default)​

One exporter per managed host.

What the mode deploys:

ComponentPlacement
node-exportermin 0, recommended 3

Install this service​

The install wizard of the Navin Manager plans, validates and runs the installation; you need the services:install permission on the cluster.

  1. Open the wizard. In Clusters, choose the row action Install services of the target cluster. The wizard opens on its first step, Service.

  2. Choose the service. On the Service step, select Node exporter. The card shows the licence Apache-2.0.

  3. Choose the hosts and the mode. On the Hosts step, tick the hosts, then choose the Mode: every-host (default). Each mode deploys the components listed in Installation methods and modes.

  4. Bindings. This service has no dependency: the Bindings step has nothing to bind.

  5. Configure. On the Configure step, review the parameters (see Configuration parameters). Passwords left empty with a generated default are generated and sealed by the Manager.

  6. Review and install. On the Install step the Manager validates the plan and shows the installation order; when it says "The plan is valid. Ready to install.", choose Install. A highly available mode is installed only when its HA checks pass.

  7. Verify. The operation ends when the health checks of every instance pass (see Health checks); the service then shows as running in Services. Open the service and choose Run the smoke test in the Checks card: Scrapes the metrics and checks that the CPU, memory and file system collectors answer with values.

High availability​

Clusterper host (per-host)
High availabilityper host (per-host)
Failovernone (none)
Replicationnone (none)
Quorumnone (none)
Discoverystatic (static)
Entry pointper host (per-host)
Official documentationhttps://github.com/prometheus/node_exporter

Topology per mode​

ModesHighest catalog levelDistributionQuorum componentFault domainsDescription
every-hostha (ha)per host (per-host)--One agent on every host: each host covers itself, the loss of a host only loses its own coverage.

Notes​

  • Each exporter reports its own host only; Prometheus alerts when an exporter stops answering.

Configuration parameters​

General​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
Metrics port (port)port9100-nononoPort of /metrics.
systemd collector (systemd_collector)booltrue-nononoReport the state of the navin-* systemd units.
TLS (tls_enabled)boolfalse-nononoServe /metrics over HTTPS (--web.config.file) with a certificate issued by the manager CA; Prometheus then scrapes it in https and verifies it with that CA.

Endpoints​

EndpointSchemeComponentPortPathTLS parameterBinding parametersBinding secretsProvisioning command
metricshttpnode-exporter9100 (port)/metricstls_enabled---

Health checks​

Liveness (per instance)​

ComponentCheckDetails
node-exporterHTTP {{ 'https' if config.tls_enabled else 'http' }}://{{ host.fqdn if config.tls_enabled else (host.ip or '127.0.0.1') }}:{{ config.port }}/metricsExpected 200; 20 retries; interval 1 s; timeout 3 s

Readiness (service check)​

CheckDetails
HTTP {{ 'https' if config.tls_enabled else 'http' }}://{{ host.fqdn if config.tls_enabled else (host.ip or '127.0.0.1') }}:{{ config.port }}/metricsExpected 200; Expected node_exporter_build_info

Smoke test​

Scrapes the metrics and checks that the CPU, memory and file system collectors answer with values. (node-exporter: cpu, memory, filesystem)

Preflight checks​

CheckTypeMeaningSeverityComponents
port_freeport_free {"param": "port"}port 9100 free on the hostblockingevery component

Uninstall​

Paths removed when the data is purged: {{ paths.log }}.

Upstream documentation​