[ZBX-20980] system.cpu.util shows different value than Task Manager on Windows server Created: 2022 May 02 Updated: 2024 Apr 10 Resolved: 2022 Jul 28 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Agent (G) |
Affects Version/s: | 5.0.23, 6.0.4, 6.2.0beta1 |
Fix Version/s: | 6.4 (plan) |
Type: | Problem report | Priority: | Trivial |
Reporter: | Stefan Flores | Assignee: | Aleksejs Sestakovs |
Resolution: | Fixed | Votes: | 0 |
Labels: | agent, cpu, load, windows | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
||||||||
Issue Links: |
|
||||||||
Team: | |||||||||
Sprint: | Sprint 89 (Jun 2022), Sprint 90 (Jul 2022) | ||||||||
Story Points: | 0.125 |
Description |
We are monitoring Windows servers with Zabbix agent. In some cases (not all) we see that the values collected by system.cpu.util are different from the Performance charts of the task manager and also when collecting the same value from the performance counters.
Environment:
Steps to reproduce:
Result: Here are two screenshots of two different servers
Expected: |
Comments |
Comment by Stefan Flores [ 2022 May 02 ] |
Used Zabbix items
Server A
Server B |
Comment by Edgar Akhmetshin [ 2022 May 03 ] |
Hello Stefan, Thank you for reporting the issue. Could you please provide raw values from Zabbix history and from perf_counters, also specify Windows name, version, build version. Regards, |
Comment by Andris Mednis [ 2022 May 03 ] |
Can you compare with Perfmon data? |
Comment by Stefan Flores [ 2022 May 03 ] |
Here are the latest 500 value Agent item
Perf_counter
Screenshot of task manager at the same time |
Comment by Edgar Akhmetshin [ 2022 May 05 ] |
Hello Stefan, Confirmed. Regards, |
Comment by Stefan Flores [ 2022 May 05 ] |
It is a virtual machine and the underlying HW has 2 CPU with 96 cores. BTW: the monitored virtual machine is "Windows Server 2019 Standard, version 1809, OS build 17763.2686"
I hope this helps |
Comment by Michael Veksler [ 2022 Jul 22 ] |
Documentation update available in 6a7226a3c18 |
Comment by Martins Valkovskis [ 2022 Jul 25 ] |
It has been decided to document that the proc.cpu.util[] item on Windows uses the Processor Time performance counter, while since Windows 8 its Task Manager shows CPU utilization based on the Processor Utility performance counter; in previous versions it was the Processor Time counter. The documentation of the proc.cpu.util[] item has been updated accordingly for the supported versions: 4.0, 5.0, 6.0, 6.2, 6.4. |