Is your feature request related to a problem? Please describe.
The pci.bus_id is a value like 00000000:71:00.0. Because of this it can't be converted to a numerical value and is not part of the metrics produced. This value is useful to identify the slot a GPU card is in on a multi-GPU setup when troubleshooting GPU issues. The GPU UUID is not found anywhere on the GPU card making it less useful when trying to locate the actual physical card.
Describe the solution you'd like
I would like to include the pci_bus_id in the requiredFields making it present in the infoMetric as a label.
Describe alternatives you've considered
The pci.bus_id can be reconstructed from the disparate pci data points that are provided as metrics from the exporter. However, it is difficult to convert decimal to hex in promQL and concatenating the strings is also less than ideal. So far I haven't been able to get it working properly using a recording rule or directly using promQL in a Grafana dashboard.
Additional context
I have a local branch with these changes and am happy to make a fork and pull request if this seems like something you would consider doing.
Is your feature request related to a problem? Please describe.
The pci.bus_id is a value like
00000000:71:00.0. Because of this it can't be converted to a numerical value and is not part of the metrics produced. This value is useful to identify the slot a GPU card is in on a multi-GPU setup when troubleshooting GPU issues. The GPU UUID is not found anywhere on the GPU card making it less useful when trying to locate the actual physical card.Describe the solution you'd like
I would like to include the pci_bus_id in the requiredFields making it present in the infoMetric as a label.
Describe alternatives you've considered
The pci.bus_id can be reconstructed from the disparate pci data points that are provided as metrics from the exporter. However, it is difficult to convert decimal to hex in promQL and concatenating the strings is also less than ideal. So far I haven't been able to get it working properly using a recording rule or directly using promQL in a Grafana dashboard.
Additional context
I have a local branch with these changes and am happy to make a fork and pull request if this seems like something you would consider doing.