openshift/node_exporter

Exporter for machine metrics

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 4 minutes ago
Added to GitGenius on June 23rd, 2023
Created on September 1st, 2017
Open Issues & Pull Requests: 2 (+0)
Number of forks: 21
Total Stargazers: 4 (+0)
Total Subscribers: 100 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 27.7 days
Mean response time: 27.7 days
90th percentile: 27.7 days
Tracked items: 1

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 88 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • tide/merge-blocker (9)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Node exporter is a Prometheus exporter that collects hardware and operating system metrics from Unix-like systems, written in Go with pluggable metric collectors.

The tool solves the problem of exposing machine-level observability data to Prometheus monitoring systems. It gathers metrics from the kernel and hardware through a set of modular collectors that can be individually enabled or disabled. The exporter listens on HTTP port 9100 by default and exposes metrics in Prometheus format. Its pluggable architecture allows operators to select only the collectors relevant to their infrastructure, reducing overhead and noise.

Adoption suits teams running Prometheus-based monitoring on Linux systems who need visibility into host-level resource utilization, hardware status, and operating system behavior. The tool is available through standard Linux distribution package managers on Enterprise Linux variants and Fedora, and can be deployed via Ansible automation or in containerized environments with appropriate namespace and mount configuration. For Windows environments, the README recommends the Windows exporter instead. GPU metrics require a separate tool, prometheus-dcgm. Containerized deployments require careful configuration to monitor the host system rather than the container itself, including bind-mounting host filesystems and potentially adding Linux capabilities depending on which collectors are needed.

The project's issue tracker is dominated by merge-blocker labels, indicating that blocking issues receive focused attention before changes are merged.