What is the primary role of the Node-exporter?

What is the primary role of the Node-exporter?

• A. To collect business metrics
• B. To provide hardware and OS metrics from the Kernel
• C. To transform metrics into dashboards
• D. To manage Kubernetes config maps

Answer: (B)

The Node-exporter is a Prometheus exporter that collects host-level metrics directly from the node’s kernel. It reads data from the system sources (like /proc and /sys) to expose metrics about hardware and OS activity—CPU usage, memory, disk I/O, network statistics, load, and other kernel-level counters—via an HTTP endpoint that Prometheus can scrape. It doesn’t gather business/application metrics, it doesn’t transform metrics into dashboards, and it doesn’t manage Kubernetes resources like config maps. In Kubernetes, it’s typically deployed as a DaemonSet to collect these node-wide metrics from every node.

The Node-exporter is a Prometheus exporter that collects host-level metrics directly from the node’s kernel. It reads data from the system sources (like /proc and /sys) to expose metrics about hardware and OS activity—CPU usage, memory, disk I/O, network statistics, load, and other kernel-level counters—via an HTTP endpoint that Prometheus can scrape. It doesn’t gather business/application metrics, it doesn’t transform metrics into dashboards, and it doesn’t manage Kubernetes resources like config maps. In Kubernetes, it’s typically deployed as a DaemonSet to collect these node-wide metrics from every node.