PRTG Manual: VMware Host Hardware (WBEM) Sensor
The VMware Host Hardware (WBEM) sensor monitors information about the hardware of an ESXi server using Web-based Enterprise Management (WBEM).
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: VMware Host Hardware (WBEM)
- French: VMware matériel du serveur hôte (WBEM)
- German: VMware Host Hardware (WBEM)
- Japanese: VMware ホストハードウェア(WBEM)
- Portuguese: Hardware de host VMware (WBEM)
- Russian: Аппаратные средства узла VMware (WBEM)
- Simplified Chinese: VMware 主机硬件 (WBEM)
- Spanish: Hardware de host VMware (WBEM)
- This sensor has a high performance impact. We recommend that you use no more than 200 of this sensor on each probe.
- This sensor requires that the CIM interface is enabled on the ESXi host. As of ESXi 6.5, you must manually enable CIM.
- We recommend Windows Server 2012 R2 on the probe system for best performance of this sensor.
- This sensor requires credentials for Linux/Solaris/macOS (SSH/WBEM) systems in the settings of the parent device.
- This sensor requires that the parent device is a VMware ESXi server as of version 5.2.
- This sensor only supports IPv4.
- This sensor uses lookups to determine the status values of one or more channels.
Requirement |
Description |
---|---|
To access the ESXi host and retrieve monitoring data via WBEM, this sensor requires that the CIM interface is enabled on the ESXi host. On ESXi 6.5, CIM is disabled by default, so you must manually activate it.
|
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.
|
Parent Tags |
The tags that the sensor inherits from its parent device, parent group, and parent probe.
|
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.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
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 ( |
Setting |
Description |
---|---|
Hardware Element |
The hardware element that this sensor monitors. |
Automatic Sensor Status |
Define if the sensor changes its status depending on the health status reading:
|
Result Handling |
Define what PRTG does with the sensor result:
|
Setting |
Description |
---|---|
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.
|
Graph Type |
Define how different channels are shown for this sensor:
|
Stack Unit |
This setting is only visible if you select Stack channels on top of each other above. 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. |
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.
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.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
For more information, see section Root Group Settings, section Access Rights.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Current |
The current |
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 |
Healthstate |
The health status
|
Power |
The average host power usage |
Rotational Speed |
The fan RPM |
Temperature |
The temperature |
KNOWLEDGE BASE
Why are my VMware sensors not working after upgrading to VCSA 6.5 U1?
How do I enable the CIM interface on VMware ESXi 6.5?
What security features does PRTG include?