In windows server APMIA CPU:TotalUtilPercent always showing 0%
search cancel

In windows server APMIA CPU:TotalUtilPercent always showing 0%

book

Article ID: 384137

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

Post the crowd strike issue in windows in july 2024in few windows server   APMIA CPU:TotalUtilPercent is always 0% and CPU core metrics also not displaying also not showing min max values as shown in the screen shot.

Metric Screenshot:

 

Environment

APMIA(23.3 and 24.x) +host monitor extension

Win 2019 standard under 

Cause

From the debug of sysedge and system log we have found below:

from the logs, when we quried for cpu(.3.6.1.4.1.546.13.1.1.1) we are getting the below error.

0356040 2024-11-06 05:47:49.57 [D]-2d94- se/snmp_vars.c[342]        : getStatPtr(): Looking for OIDs '1.3.6.1.4.1.546.13.1.1.1'
0356041 2024-11-06 05:47:49.57 [W]-2d94- se/nt_kernel.c[3167]       : get_processor_stats_perf(): get_proc_stats: Processor Object was not not found in Performance Registry, CPU utilization is not available
0356042 2024-11-06 05:47:49.57 [W]-2d94- se/nt_kernel.c[3248]       : prepare_cpu_structures(): Failed getting number of CPUs. Got -1. CPU statistics are not available!
0356043 2024-11-06 05:47:49.57 [W]-2d94- se/nt_kernel.c[3167]       : get_processor_stats_perf(): get_proc_stats: Processor Object was not not found in Performance Registry, CPU utilization is not available
0356044 2024-11-06 05:47:49.57 [W]-2d94- se/nt_kernel.c[3248]       : prepare_cpu_structures(): Failed getting number of CPUs. Got -1. CPU statistics are not available!

Resolution

1> We have cross verified that the  performance object for process is enabled for windows system via checking 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfProc\Performance registry key values and performance monitor utility output data

2> So tried resetting resting all the performance counter. with the below command followed by system re-boot.

Open the command prompt, then 

cd c:\windows\system32 

lodctr /R 
cd c:\windows\sysWOW64 

lodctr /R

3> Once the system is up then restarted the APMIA  and sysedge  service ,the metric started reporting .