CPU service (local API, SNMP, WMI)

When this service has a scan interval of less than 5 minutes, the agent may take longer than the scan interval to gather the metrics. As a result, you may notice some scan intervals are not populated.

The CPU service monitors the utilization rate of the central processing unit on a device. Depending on the device, the CPU service will gather information using one of:

  • Local API call,
  • SNMP,
  • WMI.

If an agent is installed on the device, local API calls will be used to collect data.

The CPU service reports the average CPU usage on a device. For devices that have multiple CPUs, the CPU service reports on the average CPU usage across all CPUs for the scan interval.

For information on the CPU (Cisco) service, see CPU (Cisco).

Service TypeLocal APISNMPWMI
Instances on a Device8
Supported Systems/ApplicationsWindows devicesWindows devices and devices that support the HOST-RESOURCES MIBWindows devices
Device Class for CPU (Local API)Server - Generic, Workstation - Generic, Laptop - Windows, Server - Windows, and Workstation - WindowsServer - Generic, Workstation - Generic, Other, Printer, Scanner/Camera, Switch/Router, Laptop - Windows, Server - Windows, and Workstation - WindowsLaptop - Windows, Laptop - Windows, Server - Windows, and Workstation - Windows
Monitored ByWindows agentWindows probe, Red Hat Enterprise Linux or macOS 10.x agentWindows probe, Windows agent
Minimum Scan Interval1 minute
Scan Interval60 minutes
Processor NumberThe ID number of the processor that you would like to monitor.n/an/a
Processor Indexn/aThe index of the processor to monitor.n/a
Processor NameA unique identifier, which represents the processor.

Properties queried and calculations performed (WMI only)

Namespaceroot\cimv2
WMI ClassWin32_Processor
WMI Property 0LoadPercentage

OID/Calculation (SNMP only)

Metric NameOID/CalculationDescription
CPU Usage (%) 1.3.6.1.2.1.25.3.3.1.2The usage of the CPU, expressed as a percentage.

Configure the processor index

To obtain the processor index, walk the object ID .1.3.6.1.2.1.25.3.3.1.2 on the target device's address to determine which indices are available for monitoring.

.1.3.6.1.2.1.25.3.3.1.2.1 50

.1.3.6.1.2.1.25.3.3.1.2.2 10

There are two indices in this case-"1" and "2".

To monitor both processors, add the service to the device and enter 1 for the Processor Index. Add the service a second time and enter 2 for the Processor Index.