The Checkmk agent uses Windows Counter ID 238 (Processor) for collecting CPU Utilization. This is fine, however on VM hosts this only captures the CPU utilization of the host itself, excluding overhead from VMs. This is not very useful when trying to monitor the actual host.
Is it possible to change this in config somewhere to a different counter ID. 1950 Processor Utility for example captures the total CPU utilization. I tried to just change the counter ID in the check_mk.yml file, however this results in an error:
Missing monitoring data for check plugins: winperf_processor_utilWARN
What is not possible is to use the other counter for the same check. That leads to the error you saw in your test.
First step is - output to counter as a new winperf section inside the agent.
For this it is important to query the base counter. With your counter ID 1950 the base counter is Processor Information (1896).
I checked this here with one HyperV and get some output that looks valid.
The line starting with number 54 is the counter you wanted.
In the third line you see all the instance names.
Now we need a check that processes this data
Inside the yaml File the definition looks this way
That’s correct, without an own check who uses this data you will see nothing. As i have also some HyperV here inside a monitoring i will take a look how much work is to do for a check with this data.
Processor and Processor Information are normally the same informations. The later one is only separated for each NUMA node.
If you look at booth perf counter objects inside Windows you should see the same values.
Here you see as an example that booth counters output the same
Hmm okay. Let me know if you find a way to get total cpu utilisation into checkmk. I really want to be able to see the sum the host OS plus VM usage as total CPU utilisation as opposed to just the host OS.
I can’t think of many scenarios where you’d want to use this counter as the default. If anyone out there knows how to get this working, please let me know.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.