WMI sensors listing incorrect entities and no values

Modified on 2025-06-10 12:53:21 +0200

Hello! I have deployed monitoring for a slightly complex remote site which is only accessible via a gateway. WMI sensors have been applied and they have populated with the entries expected such as CPU cores and disk letters for each server however the data for these is not being received with no clear error reason. Also i am suspicious of the values provided as it is it is only listing C:\ and E:\ on multidisk sensors and that certain servers have 20+ cpu sockets.

Please could you provide any guidance on why this is happening?

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hi Sam,

What exactly are you seeing in the Sensor? WMI Processor has issues with more than 12 sockets iirc. Do you see the same behavior with the SNMP sensor equivalents? ----- Kind regards,
Stephan Linke, Tech Support Team

Apr, 2018 - Permalink

Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

WMI sensors listing incorrect entities and no values

Article CommentsAttention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Search

Attention

Related Articles

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.