Problem
When using device names like sdX and nvmeXnX, after making changes to the hardware a device like sda or nvme1n1 may not be the same device it was before. In Netdata however, this is what happens: temperature data and much more now shows up under a different device.
Description
The Linux kernel has been offering device names which include the protocol, manufacturer and serial number for many years and for use cases like storage administration, using these device names instead of the simpler device names or UUIDs is most useful for tracking inventory and identifying failures. It would make the most sense and be consistent for Netdata also to use these names.
Short excerpt:
lrwxrwxrwx 1 root root 9 Jul 13 13:29 /dev/disk/by-id/ata-WDC_WD40EFRX-68N32N0_WD-xxxxxxxxxxxx -> ../../sdd
lrwxrwxrwx 1 root root 13 Jul 13 13:29 /dev/disk/by-id/nvme-Lexar_SSD_NM790_4TB_xxxxxxxxxxxxxxxxxx -> ../../nvme2n1
In addition it is cumbersome to identify what sda or nvme1n1 currently is. Good administrators however, should keep track of serial numbers their devices use and they are printed on each device, so there is no need to reinvent the wheel (by coming up with numbers and schemes or writing UUIDs on the hardware ) and in case of hardware failures one has to look up and provide the respective serial number to the manufacturer or supplier anyway.
It just enforces best practices.
Importance
really want
Value proposition
- Better and consistent tracking of devices and failures for storage administrators
Proposed implementation
No response
Problem
When using device names like sdX and nvmeXnX, after making changes to the hardware a device like sda or nvme1n1 may not be the same device it was before. In Netdata however, this is what happens: temperature data and much more now shows up under a different device.
Description
The Linux kernel has been offering device names which include the protocol, manufacturer and serial number for many years and for use cases like storage administration, using these device names instead of the simpler device names or UUIDs is most useful for tracking inventory and identifying failures. It would make the most sense and be consistent for Netdata also to use these names.
Short excerpt:
In addition it is cumbersome to identify what sda or nvme1n1 currently is. Good administrators however, should keep track of serial numbers their devices use and they are printed on each device, so there is no need to reinvent the wheel (by coming up with numbers and schemes or writing UUIDs on the hardware ) and in case of hardware failures one has to look up and provide the respective serial number to the manufacturer or supplier anyway.
It just enforces best practices.
Importance
really want
Value proposition
Proposed implementation
No response