-
Change Request
-
Resolution: Unresolved
-
Trivial
-
None
-
None
-
None
-
Windows and others
Current implementation of system.cpu.discovery discovery rule has limitations. It provides only
{#CPU.NUMBER} and {#CPU.STATUS}
One example, where it might be potentially not sufficient is NUMA enabled systems with more than 64 logical CPUs like this one ZBX-25503.
If the information provided by the standard agent item keys like system.cpu.util is not sufficient for a user's task, the user might want to use Windows performance counters like this one:
perf_counter[\Processor Information(<NUMA node idx>,<CPU idx in NUMA node>)\% Privileged Utility]
<NUMA node idx>,<CPU idx in NUMA node> are not provided by system.cpu.discovery.
A new generation of system.cpu.util should be created. It might be called system.cpu.get. It should return the new style JSON with no macros and JSONPath should be used to discover items.
It should be universal. It should work for Windows and other platforms. Details should be elaborated while creating the specification.
- related to
-
ZBX-25503 Windows agent fails to monitor CPU related counters starting with 49 thread/core on NUMA enabled machine
- Sign off by Support