Info |
---|
This article explains how to reset the counter of CPU cores when added to a Windows VM. |
Status |
---|
colour | Green |
---|
title | LAST TESTED ON CHECKMK 2.0.0P1 |
---|
|
Problem
Since the increase of the cores on the Windows VM, the graphs show constant values without any change.
The Windows Agent executes the following commands to get the values:
Code Block |
---|
|
Get-WmiObject -class Win32_PerfRawData_PerfOS_System -namespace root\cimv2 |Format-List *
|
Code Block |
---|
|
Get-WmiObject -class Win32_PerfRawData_PerfOS_System -namespace root\cimv2 |Format-List ProcessorQueueLength |
Solution
Checkmk is caching these values with the corresponding timestamp. In this case, the new timestamp has a smaller value than the new one. That's why Checkmk is always presenting the old/constant values. We suspect that this is because of the core modification. It looks like Windows is resetting some system counters.
To solve this, you need to remove the cached counter file:
Stop the site
Code Block |
---|
|
root@mylinuxhost~# omd stop <SITENAME> |
.
As site user, you should find this file: ~/tmp/check_mk/counters/<HOSTNAME>. In this file, you need to delete the following section:
Code Block |
---|
language | bash |
---|
theme | RDark |
---|
title | ~/tmp/check_mk/counters/<HOSTNAME> |
---|
|
('wmi_cpuload', None, 'load_5min'): (29632775.478311848, 18.056825022850912), ('wmi_cpuload', None, 'load_15min'): (29632775.478311848, 15.787631011576273), |
.
Attached, you will find a screenshot with the marked section:
.
Start the site
Code Block |
---|
|
root@mylinuxhost~# omd start <SITENAME> |
Related articles
Filter by label (Content by label) |
---|
showLabels | false |
---|
max | 5 |
---|
spaces | KB |
---|
showSpace | false |
---|
sort | modified |
---|
reverse | true |
---|
type | page |
---|
cql | label in ( "windows_agent" , "windows" , "counter" , "wmi" ) and type = "page" and space = "KB" |
---|
labels | windows windows_agent counter wmi |
---|
|