prometheus / prometheus/node_exporter
feat(ethtool): query SFP module diagnostics from EEPROM
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.8k
- Forks
- 2.7k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 8
Description
Motivation
SFP transceivers expose live diagnostic data through the Digital Diagnostics Monitoring (DDM) interface, accessible today via:
$ sudo ethtool -m enp5s0f1
...
Laser bias current : 32.450 mA
Laser output power : 0.4374 mW / -3.59 dBm
Receiver signal average optical power : 0.5784 mW / -2.38 dBm
Module temperature : 41.55 degrees C / 106.78 degrees F
Module voltage : 3.3715 V
...
It can provide crucial data by identifying failing transceivers and monitoring the thermal health of modules.
Spec links
There are few specifications describing encoding of SFP diagnostics data.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ethtool -m enp5s0f1 output shown in the issue and read the linked SNIA specifications for SFP diagnostic encoding. Determine how the EEPROM values should be queried and represented by node_exporter; done means exposing the relevant live diagnostic data reliably, with behavior verified against an SFP module.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- networking, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100