You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(I am not sure if this better belongs here or node-exporter, feel free to move the issue to the other repo.)
On most ARM devices there are no DMI tables and when using things like u-boot emulating UEFI they are still incomplete. Thus /sys/class/dmi/id/product_serial is not available/empty. Alternatively, however, /sys/firmware/devicetree/base/serial-number is usually available on those devices and also contains a serial number. In case the former does not exists it should fall back to the latter.
The text was updated successfully, but these errors were encountered:
I don't know about this nor what 'devicetree' is exactly, but instead of falling back we should probably explicilty expose devicetree entries, so the caller of procfs can decide how to reach e.g serial numbers
The exposed serial numbers semantically represent the same thing as those in the DMI tables for UEFI machines. As such other projects like systemd also treat them equivalent
I would also be fine with exposing them separately in this lower level module. In that case however I would also create an issue at the node-exporter repo to treat them equivalently there
(I am not sure if this better belongs here or node-exporter, feel free to move the issue to the other repo.)
On most ARM devices there are no DMI tables and when using things like u-boot emulating UEFI they are still incomplete. Thus
/sys/class/dmi/id/product_serial
is not available/empty. Alternatively, however,/sys/firmware/devicetree/base/serial-number
is usually available on those devices and also contains a serial number. In case the former does not exists it should fall back to the latter.The text was updated successfully, but these errors were encountered: