CPU Core Sensors - OS Test

The CPU Core Sensors - OS Test monitors the health and performance of each CPU core on the target system. For every CPU core, it reports key metrics such as clock speed, temperature, load utilization, power usage, and bus clock speed. If the values of these measures are abnormal, they may indicate an overloaded or overheating core, leading to performance issues or potential hardware damage. Comparing values across CPU cores helps identify underperforming or stressed cores. This way the test enables adminsitrators to proactively monitor the system and ensure optimal CPU utilization.

Target of the test : A Physical Desktop Group

Agent deploying the test : A remote agent

Output of the test: One set of results for each CPU core of the target system being monitored.

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed.
Host	The nick name of the Physical Desktop Group component for which this test is to be configured.
Port	Refers to the port at which the specified host listens to. By default, this is NULL.
Report Powered OS	This flag is relevant only for those tests that are mapped to the Physical Desktops Details layer. If this flag is set to Yes (which is the default setting), then the 'inside view' tests will report measures for even those Windows physical machines that do not have any users logged in currently. Such desktops will be identified by their name and not by the username_on_physicalmachinename. On the other hand, if this flag is set to No, then this test will not report measures for those physical machines to which no users are logged in currently.
Report By User	This flag is set to Yes by default. The value of this flag cannot be changed. This implies that the physical machines in environments will always be identified using the login name of the user. In other words, in VDI environments, this test will, by default, report measures for every username_on_physicalmachinename.
Exclude	By default, this parameter is set to none. This means that the test will monitor all the applications that are launched on the target server, by default. If you want the test to disregard certain applications when monitoring, then provide a comma-separated list of process names that correspond to the applications you want to ignore, in the Exclude text box. For instance, your specification can be: winword.exe,js.exe,taskmgr.exe. Your specification can include wild card patterns as well. For example: win,js,task
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. For instance, if you set to 6:1, it means that detailed measures will be generated every time this test runs, and also every time the test detects a problem.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Clock Speed	Indicates the current speed of this CPU core.	MHz	A very low value for this measure indicates that the CPU core is slow. Comparing the value of this measure across CPU cores will point you to that CPU core that is currently very slow.
Temperature	Indicates the current temperature of this CPU core.	Celsius	The value of this measure should be within optimal range. A sudden/gradual increase in the value of this measure may impact the functioning of the CPU core and needs to be attended to immediately.
Load Utilized	Indicates the percentage of load handled by this CPU core.	Percent	Comparing the value of this measure across the CPU cores will help you identify the CPU core that is overloaded.
Power utilized	Indicates the power consumed by this CPU core.	Watts
Bus Clock Speed	Indicates the speed at which this CPU core communicates with the system bus.	MHz