Summary: This post outlines how hardware metrics from HP systems can be monitored. It explains native capabilities, limitations, and alternatives such as SNMP or external integrations.
For a customer, we have the requirement to monitor physical HP servers and act on health errors of the hardware. It’s about the health of disks, the motherboard, the power supplies, the batteries, etc.
On the server itself, Windows (all kinds of versions) is the operating system, and a Dynatrace OneAgent is active on the servers.
We don’t have HPE OneView installed on the hardware.
For the extension ensure the general installation prerequisites are fulfilled such firewall, network connectivity ,..etc and then start adding the intended servers.
If there is applicability to install oneagent, proceed with oneagent deployments.
If the license consumption doesn’t matter proceed with OA deployments, otherwise install the extension.
SNMP traps may be an option for you - forward traps from the ILO (HPE physical server console), or Blade enclosure console to the Environment ActiveGate.
Downside with this approach is then identifying the SNMP OID values that you need to create a problem notification for in Dynatrace and there may be specific OIDs on specific hardware types that you may need.
The ILO itself can use Network Availability Monitor to confirm its “reachable”, or a HTTPS check if you want more detailed check that the ILO is alive.
HPE servers do have an on-host hardware agent (provided by HPE) that pulls hardware issues into the system log but this only works if the OneAgent is functioning. You need to identify the rules to extract the log events from the system log to create the Dynatrace Problem notifications. These rules may be different by hardware type and operating system.