In some Windows Systems, the Service "Processor Queue" might vanish, and the "Processor Queue" goes UNKN. In this case, we will give you a short guidance. |
Open the Windows agent's log file and see if you find this:
2021-08-03 17:15:35.063 [Err ] Timeout [3] seconds broken when query WMI ... ... ... 2021-08-03 15:02:44.435 [Warn ] Object 'Win32_PerfRawData_PerfOS_System' in 4ms sends NO DATA 2021-08-03 15:02:44.436 [Warn ] Sub Section 'system_perf' has no data to provide, status = [2] |
You will need PowerShell to run the following commands! |
You will find the source code of the Windows Agent in our GitHub. There you will find all the System and Performance counters. For wmi_cpuload, we need the following counters:
root@mylinuxhost:/# grep -A5 "CPULOAD" /home/mylinuxuser/git/check_mk/agents/wnx/src/engine/providers/wmi.cpp
// WMI CPULOAD group
{"system_perf", //
{kWmiPathStd, L"Win32_PerfRawData_PerfOS_System"}},
{"computer_system", //
{kWmiPathStd, L"Win32_ComputerSystem"}},
|
Now you can run both commands. What's the output? Do you see all the data like described here: Microsoft win32 Documentation
Get-WmiObject -class Win32_PerfRawData_PerfOS_System -computername WIN-MOP95J96UQA -namespace root\cimv2 |Format-List * Get-WmiObject -class Win32_ComputerSystem | Format-List * |
How long does the query run? You can use the measurement command for this:
Measure-Command {Get-WmiObject -class Win32_PerfRawData_PerfOS_System -computername WIN-MOP95J96UQA -namespace root\cimv2 |Format-List *}
Measure-Command {Get-WmiObject -class Win32_ComputerSystem | Format-List *} |
WMI Database is broken → Use the WMI Explorer for further debugging
You can try these commands, but be careful
Rebuilding WMI repository
winmgmt /clearadap winmgmt /resyncperf |
Required tools:
|
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|