Redfish Server Monitoring

Last updated - 26 June, 2026

LogicMonitor’s Redfish Server Monitoring package uses the DMTF Redfish REST API to monitor the health, status, and performance of server hardware managed through Baseboard Management Controllers (BMCs). The package provides monitoring for CPUs, GPUs, memory modules, storage controllers, physical drives, fans, temperature sensors, power supplies, network adapters, network interfaces, and PCIe devices.

By using the Redfish standard, the package provides a unified monitoring solution across multi-vendor server environments without requiring vendor-specific SNMP MIBs or proprietary agents. The package includes support for vendor-specific Redfish implementations commonly found in Dell iDRAC, HPE iLO, and Lenovo XClarity Controller platforms.

The package is validated against Dell iDRAC 9, HPE iLO 5 and iLO 6, and Lenovo XClarity Controller platforms. Any server hardware exposing a Redfish-compliant API is compatible with the core monitoring modules.

Requirements for Redfish Server Monitoring

To use the Redfish Server Monitoring package, you need the following:

• A LogicMonitor user with the Install and Manage permissions for the resource and relevant Collector in the Modules role permissions
• A read-only Redfish user account
• LogicMonitor Collector version 32.400 or later, or the LogicMonitor_Collector_Snippets DataSource must be installed
• Your Collector can communicate with the target BMC over HTTPS (default port 443)
• The resource represents the BMC management interface (for example, Dell iDRAC, HPE iLO, or Lenovo XClarity Controller) rather than the operating system IP address
• The Redfish API (DSP0266 v1.6 or later) enabled on the target BMC

Add Resources into Redfish Server Monitoring

Add the BMC management interface as a resource in LogicMonitor. The resource hostname or IP address should be the BMC management IP address, such as an iDRAC, iLO, or XClarity Controller management interface, rather than the server operating system IP address.

For more information on adding resources into monitoring, see Adding Resources.

Assign Properties to Redfish Server Resources

Configure the following properties on the monitored resource:

Property	Required	Description
redfish.user	Yes	Redfish API username
redfish.pass	Yes	Redfish API password
redfish.port	No	HTTPS port used by the Redfish API. Defaults to 443. Configure this property if the BMC exposes Redfish on a non-standard port.
redfish.ip	NoNote: Only required if redfish.ip differs from system.hostname.	Overrides the hostname or IP address used for Redfish API requests. Defaults to the resource hostname.

For more information, see Resource and Instance Properties.

Import LogicModules

Import all Redfish LogicModules from the LogicMonitor Exchange or public repository.

If the modules are already present in your environment, verify that the latest versions are installed.

When the LogicModules are imported and all requirements have been met, data collection begins automatically.

For more information, see Modules Overview.

Troubleshooting

Issue	Resolution
Redfish category not being set	Verify that both redfish.user and redfish.pass are configured on the resource. Verify the redfish.ip matches or is overriden to match the system.hostname. The addCategory_Redfish PropertySource validates connectivity to the Chassis, Systems, and Managers endpoints. If all four checks fail, the Redfish category does not apply. To validate connectivity manually, browse to https://<BMC_IP>/redfish/v1/.
Authentication errors (401)	Verify that the configured credentials are correct, the BMC account is not locked, and the account has permission to access the Redfish API.
Missing instances	Run Active Discovery manually. Verify that the BMC firmware exposes the required Redfish endpoints and supports the monitored hardware component. Older firmware versions may not expose endpoints such as /PCIeDevices or /NetworkAdapters.
Missing vendor-specific data	Some datapoints are only available through vendor-specific Redfish extensions. Missing values for unsupported vendors are expected behavior.
Collect additional diagnostic information	The LogicModules include debug and log modes for troubleshooting. Set debug = true when testing scripts in the Collector Debug Facility, or set log = true to write additional information to collector logs during Active Discovery and data collection. For more information, see Collector Logging and Script Troubleshooting.

LogicModules in Package

LogicMonitor’s package for Redfish Server Monitoring consists of the following LogicModules. For full coverage, import the following LogicModules into your platform:

Display Name	Type	Description
addCategory_Redfish	PropertySource	Validates Redfish connectivity and applies the Redfish category.
Redfish_Device_Info	PropertySource	Collects hardware, firmware, chassis, storage, memory, and BMC information.
Redfish CPU	DataSource	Monitors CPU health, state, and enabled core count.
Redfish GPU	DataSource	Monitors GPU health, state, and enabled core count.
Redfish Memory	DataSource	Monitors DIMM health and state.
Redfish Storage	DataSource	Monitors storage controller health and status.
Redfish Drives	DataSource	Monitors physical drive health, capacity, and media life.
Redfish Fans	DataSource	Monitors fan health and speed.
Redfish Temperatures	DataSource	Monitors chassis temperature sensors.
Redfish Voltage	DataSource	Monitors voltage sensors.
Redfish Power Consumption	DataSource	Monitors chassis power usage.
Redfish Power Supplies	DataSource	Monitors power supply health and performance.
Redfish Network Adapter	DataSource	Monitors network adapter hardware.
Redfish Network Interfaces	DataSource	Monitors network interface status and performance.
Redfish PCI	DataSource	Monitors PCIe device health and configuration.
Redfish System Logs	LogSource	Collects Redfish system log entries.
Redfish Manager Logs	LogSource	Collects Redfish manager log entries.

When setting static datapoint thresholds on the various metrics tracked by this package’s DataSources, LogicMonitor follows the technology owner’s best practice KPI recommendations.