prometheus / prometheus/node_exporter

CPU Model metrics

Open
#3,811 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
13.8k
Forks
2.7k
Avg merge
1d 23h
Merged PRs (30d)
8

Description

Hi,

I would like to monitor the CPU model information for all CPU sockets on a system using node_exporter.

For example, on a multi-socket server, I would like to be able to identify the CPU model associated with each socket, such as:

  • Socket 0 → Intel Xeon ...
  • Socket 1 → Intel Xeon ...

I could not find a node_exporter metric that exposes this information. I also checked for metrics such as node_cpu_info, but this metric does not exist in my node_exporter installation.

Could you please clarify:

  1. Is there currently a node_exporter metric that exposes the CPU model/name for each CPU socket?
  2. If it exists, what is the metric name?
  3. How can this metric/collector be enabled?
  4. If node_exporter does not currently expose CPU model information, is there a reason why this information is not provided as a metric?
  5. Would it be possible to consider adding such a metric/collector in the future?

node exporter version

/usr/local/bin/node_exporter --version
node_exporter, version 1.11.1 (branch: HEAD, revision: 0dd664dece3f8319f6bec5a221acd2c7ad13a23d)
  build user:       root@3d8697c83dd8
  build date:       20260407-15:45:19
  go version:       go1.26.1
  platform:         linux/amd64
  tags:             unknown

node exporter options:

ExecStart=/usr/local/bin/node_exporter \
    '--collector.systemd' \
'--collector.textfile' \
    '--collector.textfile.directory=/var/lib/node_exporter' \
    '--log.level=info' \
    '--log.format=logfmt' \
    '--web.listen-address=0.0.0.0:9100' \
    '--web.telemetry-path=/metrics'

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the collectors enabled in the node_exporter options and checking whether any existing metric exposes CPU model information per socket. Compare the available metrics with the requested node_cpu_info behavior; done means establishing whether this data is already available or defining the scope for a new collector or metric.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, linux
Domain
observability, operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.