What is "_Total" process and why does it show peak values of 100 or more for Windows Servers

What is "_Total" process and why does it show peak values of 100 or more for Windows Servers

CPU Utilization : The CPU Utilization attribute is obtained from the performance counter "\Processor(_Total)\% Processor Time".

\Processor(_Total)\% Processor Time :  This is the percentage of elapsed time that the processor spends to execute a non-Idle thread and shows the value of total processor utilization system-wide.


When the CPU Utilization goes above a critical threshold and has an action configured, A break-up of the CPU Utilization by individual processes list is obtained as a HTML file, which shows the "_Total" attribute which obtained from the performance counter "Process(_Total)\% Processor Time". This might usually be a higher value, or  > 100 in the case of more CPUs.



Process(_Total)\% Processor Time : This counter shows the percentage of elapsed time that all of process threads used the processor to execution instructions.The reason this value is mostly peaked or at 100 is because the Process(_Total) counter is the sum of all processes using the processor, in addition to the amount of Idle process.

The theoretical maximum that this value can obtain is calculated by the below formula:
Process(_Total)\% Processor Time  =  Number_Of_Cores  *  100

In order to obtain the \Processor(_Total)\% Processor Time from Process(_Total)\% Processor Time, the below formula can be used:

\Processor(_Total)\% Processor Time = [Process(_Total)\% Processor Time] - [Process(Idle)\% Processor Time]  / Number_Of_Cores

These performance counter values can be verified by adding them in Perfmon:









                    New to ADSelfService Plus?

                      • Related Articles

                      • Windows Server Monitor - WMI Metrics Reference Tables

                        This document lists the WMI namespaces, classes, and WQL queries used by AppManager Windows Server Monitor scripts in WMI mode. These reference tables can be used to troubleshoot WMI-related issues, validate WMI queries using WBEMTEST, verify ...
                      • Windows Monitoring - FAQ

                        This Knowledge Base article provides answers to frequently asked questions about Windows Server monitoring using WMI mode. The articles are organized by the monitoring lifecycle to help you quickly identify the relevant troubleshooting guide. ...
                      • Configuring HPE Gen10 and later servers for hardware monitoring through SNMP

                        Overview With the introduction of HPE Gen10 servers, HPE discontinued support for traditional operating system-based SNMP agents for hardware monitoring. Instead, HPE introduced the System Management Assistant (SMA) as part of the Agentless ...
                      • SQL query to display all the servers monitored except Windows in Applications Manager

                        To obtain the list of all the servers monitored other than Windows, follow the steps given below: Open SQL Management Studio. Connect to the Applications Manager database. Execute the below query in Admin or Managed server:  SELECT ...
                      • How to Fix Node.js Agent Zip Extraction Issue on Windows

                        Overview From Node.js Agent version 5.4.1 (APM version 181000 and later) onwards, some users may experience issues extracting the agent zip file on Windows systems using the default extractor. Recommended Solution To properly extract the Node.js ...