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'd appreciate a sense of direction as to how to adapt the code to monitor OEM extensions. I'm thinking particular of the Dell extensions, for which there's a tool idelloem documented here https://linux.die.net/man/8/idelloem
The text was updated successfully, but these errors were encountered:
Hi,
t depends a bit on what exactly you are trying to achieve. If you are after sensor data, you could check if adding --interpret-oem-data to the call to ipmimonitoring does the trick (see e.g. https://www.gnu.org/software/freeipmi/manpages/man8/ipmi-sensors.8.html). Alternatively, the FreeIPMI suite that the exporter uses also comes with a tool called ipmi-oem that supports certain Dell-specific commands (https://www.gnu.org/software/freeipmi/manpages/man8/ipmi-oem.8.html), but I don't see immediately what parts of that it would make sense to export to Prometheus. You could of course replace the calls to the actual tools with calls to idelloem, but then you'd need to add parsing for the output.
Can you specify what data you are interested in?
Thanks @bitfehler . I am not sure yet what we need, but the environment is heterogeneous bare-metal servers of a number of different system types (including servers from several vendors, and both amd64 and arm64 architectures).
Mostly exploring tools and trying to figure out how to explore what might be exported (at minimum, power, fans, and temperature look necessary; but who really knows what's lurking on some of this firmware until you explore it).
I'd appreciate a sense of direction as to how to adapt the code to monitor OEM extensions. I'm thinking particular of the Dell extensions, for which there's a tool
idelloem
documented here https://linux.die.net/man/8/idelloemThe text was updated successfully, but these errors were encountered: