Skip to content
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 OEM extensions #2

Open
vielmetti opened this issue Jun 20, 2018 · 2 comments
Open

Support for OEM extensions #2

vielmetti opened this issue Jun 20, 2018 · 2 comments

Comments

@vielmetti
Copy link

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

@bitfehler
Copy link
Contributor

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?

@vielmetti
Copy link
Author

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants