-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for ipmi-fru module? #127
Comments
As far as I can tell, this is all static information, right? I'd say most of this is not really a good fit for a time series database. That said, I understand it could be useful to have something like a serial number as a label someplace, so I am not generally opposed to making this available as opt-in.
Which power capacity do you mean? Are your PSUs unable to handle full load of the unit? From my experience, the bottle neck is rather the power capacity per rack or feed, which you just have to know. Can you roughly describe what kind of alert you would set up if you had all this data available? |
Meta information is okay for tsdb. If that didn't work, how would disk monitoring work? For each disk there is a meta metric, which indicates the rotation speed, interface, manufacturer, serial number. Alerting without this information would be impossible. Of course opt-in, like any module in
I agree with that, the power capacity of rack is top of bottle necks. For example, is good to know, that current load of PSU is near of 100% of PSU capacity. This will be useful information with |
@k0ste do you have an idea/opinions on how you'd shape this into metrics & labels? 1 metric per ID, with selected fields filled in.
I absolutely do want the FRU functionality, to answer some fleet questions. |
@robbat2, it seems to me that at the initial stage we need to be more restrained in metrics. I would start with: fru_baseboard_info{product_name="S2600WFT", part_number="R2208WT", serial_number="BQWF80100215", manufacturer="Intel Corporation"}
fru_baseboard_info{product_name="PowerEdge R540", part_number="0NJK2FA03", serial_number="CNFCP0087J01O7", manufacturer="DELL"}
fru_power_supply_info{part_number="H79286-007", serial_number="CNS1322A4AHCA0031", manufacturer="SOLUM CO., LTD."}
fru_power_supply_info{part_number="0V1YJ6A00", serial_number="CN1797263S3M1T", manufacturer="DELL"} Something like that is more then enough to start. After this we can check the code with zoo of baremetal servers |
yes, I wanted to be more constrained in metrics, taking only id=00h, but the catch is that each FRU item has many fields. Here's my
At the bare minimum, I'd want this exported as:
I wish |
The our SMC's have only this FRU Inventory Device: BMC FRU (ID 00h)
FRU Board Manufacturing Date/Time: 08/11/21 - 10:00:00
FRU Board Manufacturer: Supermicro
FRU Board Product Name: X11DPi-NT
FRU Board Serial Number: NM217S007782
FRU Product Serial Number: 🫠 |
Hi, everyone, when will this fru function be supported? I am currently unable to obtain the serial number of the server through ipmi_exporter, as well as other hardware information, such as the number of hard disks, memory and other information. |
ipmi-fru displays Field Replaceable Unit (FRU) Information. The FRU may hold a variety of information, such as device information, hardware information, serial numbers, and part numbers.
This may be useful, for determine PSU overall capacity & serial numbers
Currently we can't alert, when power usage near power capacity
Example FRU for Intel platform:
Example FRU for Dell platform:
Example FRU for Quanta platform:
The text was updated successfully, but these errors were encountered: