ESX host monitor, no disks?

Dear B van Haastrecht

Our WBEM sensor looks for "OMC_NumericSensor". Can you check if this metric is provided by your machine?

Hi Arne,

Storage related elements are not in OMC_NumericSensor, they are in:

VMware_Controller =  storage controller status (5 = OK)
VMware_StorageVolume = Logical volumes (5 = OK)
VMware_StorageExtent = Harddisks (5 = OK)

ResourceUrl: http://schemas.vmware.com/wbem/wscim/1/cim-schema/2/

All relevant CIM objects of an ESX server, also seen in the Hardware
tab of an ESX server:

 - CIM_ComputerSystem
 - CIM_NumericSensor
 - CIM_Memory
 - CIM_Processor
 - CIM_RecordLog
 - OMC_DiscreteSensor
 - VMware_StorageExtent
 - VMware_Controller
 - VMware_StorageVolume
 - VMware_Battery
 - VMware_SASSATAPort

Would be great if you add this to the monitor.

Still nothing on this 2 years later?

Dear EdNot,

this is a general issue with user requests: We get too many to implement them all. When we prioritize, we have to look on the demand in the big picture. The more users PRTG gets, the more suggestions we get.

I doubt that this request will be implemented in the foreseeable future, because our sensor developers work on other sensors for which we see wider usage.

Competators can monitor local disks ext in an ESX host since long time ago, do not make it look like you are inventing space technology. If PRTG would just adobt WBEM / CIM-XML you could monitor not only ESX but a lot of other devices/software as it's an open standard stil being worked and developed on.

This is by far not a niche request, ESX is THE leading hypervisor.

Dear bvanhaastrecht,

I agree. However, every line of code written, reviewed, tested and documented on some part is missing somewhere else. We have to look at the big picture and prioritize accordingly.

Because we cannot build all requested sensors ourselves, we offer our API to add custom sensors.