Content Previous Next

PRTG Manual: Redfish System Health Sensor

<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Redfish System Health Sensor

The Redfish System Health sensor monitors the system health of a Redfish Scalable Platforms Management API (Redfish)-capable server.

Redfish System Health Sensor

For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.

Sensor in Other Languages

Dutch: Redfish System Health
French: État du système Redfish
German: Redfish Systemzustand
Japanese: Redfish システム正常性
Portuguese: Funcionamento do sistema Redfish
Russian: Работоспособность системы Redfish
Simplified Chinese: Redfish 系统健康状况
Spanish: Salud del sistema Redfish

Remarks

This sensor requires credentials for Redfish in settings that are higher in the object hierarchy.

This sensor requires at least read permissions for the target system. Without sufficient permissions to a subsystem, the sensor will show the Down status.
If you want to monitor Supermicro, then this sensor requires full administrator access.

This sensor supports IPv6.

This sensor has a very low performance impact.

This sensor uses lookups to determine the status values of one or more channels.

Supporters of the Redfish standard include Dell, Eaton, Emerson, Fujitsu, HPE, Intel, Lenovo, NetApp, Supermicro, and VMware.

Basic Sensor Settings

Setting	Description
Sensor Name	Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets. If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include?
Parent Tags	The tags that the sensor inherits from its parent device, parent group, and parent probe. This setting is for your information only. You cannot change it.
Tags	Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited. It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>). For performance reasons, it can take some minutes until you can filter for new tags that you added. The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor: redfish restsensor
Priority	Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority () to the highest priority ().

Redfish Specific

The information in the Redfish Specific settings reflect the status of the system at the time of sensor creation. If any setting changes after creation, the Redfish Specific settings do not reflect the change. Add the sensor anew to update the displayed settings.

Setting	Setting
Name	The name of the system that this sensor monitors.
Model	The model of the system that this sensor monitors.
Manufacturer	The manufacturer of the system that this sensor monitors.
Serial Number	The serial number of the system that this sensor monitors.
Asset Tag	The asset tag of the system that this sensor monitors

Sensor Display

Setting	Setting
Primary Channel	Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor. You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab.
Graph Type	Define how different channels are shown for this sensor: Show channels independently (default): Show a graph for each channel. Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic. You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).
Stack Unit	This setting is only visible if you enable Stack channels on top of each other as Graph Type. Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.

Setting

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.

You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab.

Graph Type

Define how different channels are shown for this sensor:

Show channels independently (default): Show a graph for each channel.
Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This setting is only visible if you enable Stack channels on top of each other as Graph Type. Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.

Debug Options

Setting	Description
Result Handling	Define what PRTG does with the sensor result: Discard result: Do not store the sensor result. Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file name is Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites this file with each scanning interval. This option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance. In a cluster, PRTG stores the result in the PRTG data directory of the master node.

Setting

Description

Result Handling

Define what PRTG does with the sensor result:

Discard result: Do not store the sensor result.

Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file name is Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites this file with each scanning interval.

This option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.

In a cluster, PRTG stores the result in the PRTG data directory of the master node.

Inherited Settings

By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.

For more information, see section Inheritance of Settings.

Scanning Interval

For more information, see section Root Group Settings, section Scanning Interval.

Schedules, Dependencies, and Maintenance Window

You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.

Schedules, Dependencies, and Maintenance Window

For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.

Access Rights

For more information, see section Root Group Settings, section Access Rights.

Channel Unit Configuration

Which channel units are available depends on the sensor type and the available parameters. If no configurable channels are available, this field shows No configurable channels.

Channel Unit Configuration

For more information, see section Root Group Settings, section Channel Unit Configuration.

Channel List

Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.

Channel	Description
Chassis Status	The chassis status Up status: OK Warning status: Warning Down status: Critical Unknown status: Offline / Absent
Downtime	In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status
Drives Status	The drives status Up status: OK Warning status: Warning Down status: Critical Unknown status: Offline / Absent
Fans Status	The fans status Up status: OK Warning status: Warning Down status: Critical Unknown status: Offline / Absent
Memory Status	The memory status Up status: OK Warning status: Warning Down status: Critical Unknown status: Offline / Absent
PCIe Devices Status	The PCIe drives status Up status: OK Warning status: Warning Down status: Critical Unknown status: Offline / Absent
Power Supplies Status	The power supplies status Up status: Off, On, Powering Off, Powering On Unknown status: Unknown
Processor Status	The processor status Up status: OK Warning status: Warning Down status: Critical Unknown status: Offline / Absent
System Power Status	The system power status Up status: OK Warning status: Warning Down status: Critical Unknown status: Offline / Absent
System Status	The system status Up status: OK Warning status: Warning Down status: Critical Unknown status: Offline / Absent This channel is the primary channel by default.
Thermal Status	The thermal status Up status: OK Warning status: Warning Down status: Critical Unknown status: Offline / Absent

KNOWLEDGE BASE

I want to know which of my systems support the PRTG Redfish sensors. Can you help me?

https://kb.paessler.com/en/topic/89858

What security features does PRTG include?

https://kb.paessler.com/en/topic/61108