- 5 minutes to read

Monitoring CPU and CPU Cores

Learn how to monitor the utilization of your CPUs and CPU Cores and get alerts when the percentage used is too high over time

This page describes what's being monitored for CPUs in Nodinite using one or more role-based Monitor Views. Nodinite monitors the state based on user-defined thresholds, either global or specific. For managing the CPUs, remote commands are available as Actions. These help you swiftly manage reported problems. The implemented Remote Actions are further detailed on this page.

CPU items as Resources
Example list of monitored CPU-related items in a Monitor View.

Monitoring Features

  • Automatic Discovery
  • State Evaluation - Based on user-defined thresholds (percentage over time)
  • Category-based monitoring - To help you sort out the different types of CPU related items, the monitored Resources are grouped by Categories

The monitored CPU-related items are displayed within Nodinite as Resources. For example, if you have 1 CPU with 4 cores, then you will have 5 Resources in Nodinite.

  • The name of the Resources comes from the count and index of the number of CPUs

    • CPU => CPU Overall
    • Core => CPU0, CPU1...
  • All monitored CPU items belongs to one of the following 'CPU' Categories

    Category Description
    CPU Make sure the CPU is running within user-defined monitoring thresholds
    CPU Core Make sure the CPU cores are running within user-defined monitoring thresholds

    Categories
    List of CPU-related categories as a filter in a Monitor View.

  • The Application name is the Display Name from the configuration of the monitored Windows Server: ApplicationPathExample

Each item (presented in Nodinite as a Resource), and is evaluated with a state. (OK, Warning, Error, Unavailable).

From within Nodinite, you can reconfigure the state evaluation on Resource level using the Expected State feature.

NOTE: Depending on the user-defined synchronisation interval set for the Windows Server Monitoring Agent, there might be a delay before Nodinite Web Client/Monitor Views reflects upon the change. Click the Sync All button (or on the dropdown for individual agent selection) to force Nodinite to request a resynchronisation request.

Sync
Option to force Nodinite to request a resynchronization request with the monitoring agent


Monitoring CPUs

For the CPU category, the monitored state evaluates as described in the table below:

State Status Description Actions
Unavailable Service not available If the server can't be reached and evaluated either due to network or security-related problems Review prerequisites
Error Error state raised The 'CPU' is using too much resources for too long time -
Warning Warning state raised Not yet implemented -
OK Online The 'CPU' accessible and is within user-defined monitoring thresholds CPU Chart
Edit

Actions for CPU

The following Remote Actions are available for the CPU and CPU - Core Categories:

Actions

Edit thresholds

You can manage the alert thresholds for selected CPU/CPU Core resource; simply click on the Action button and then click the Edit thresholds menu item within the 'Control Center' section.

Edit thresholds Menu Action
Edit thresholds, using the 'Edit' action

Next, click the option to present the modal.

Edit thresholds modal
Example of the 'Edit thresholds' modal

Metrics

You can view some statistics about the selected CPU instance, by simply clicking on the Action button and then clicking the CPU Chart menu item within the 'Control Center' section.

CPU Chart Menu Item
Show CPU statistics, using the 'CPU Chart' action

Next, click the option to present the modal.

CPU Performance Counters
Example of CPU usage statistics

This modal is designed for the purpose of being used as a Widget in the Dashboard.

Widget on Dashboard

CPU statistics example as a Widget on the Dashboard


Monitoring CPU Cores

Monitoring CPU Cores is a more fine-grained monitoring option compared with CPU Monitoring. All monitoring options are the same, hence the previous documentation above for monitoring CPUs covers this topic.


Configuration

Use the Remote Configuration to manage the CPU configuration.

CPU tab

Click the CPU tab to manage CPU Monitoring options.
CPU Tab
Example of the 'CPU' tab

There are multiple options for Monitoring the CPU. Two major subcategories exist:

  • CPU
  • CPU Core

Manage the Monitoring options using the Remote Actions, review the 'CPU' user guide for additional information.

CPU

  • Enable CPU Monitoring - When checked, enables the Monitoring of the CPU Overall usage. Otherwise, Monitoring is disabled.
  • CPU Warning Threshold % - When the CPU usage is over this threshold for more than the configured number of seconds (CPU Duration), the evaluated state is 'Warning'.
  • CPU Error Threshold % - When the CPU usage is over this threshold for more than the configured number of seconds (CPU Duration), the evaluated state is 'Error'.
  • CPU Threshold overrun duration - The maximum allowed duration breaching the threshold (seconds).

CPU Core

  • Enable CPU - Core Monitoring - When checked, each Core in the CPU(s) will be monitored individually for this Windows Server
  • CPU Core Warning Threshold % - When the CPU Core usage is over this threshold for more than the configured number of seconds (CPU Core Duration), the evaluated state is 'Warning'.
  • CPU Core Error Threshold % - When the CPU Core usage is over this threshold for more than the configured number of seconds (CPU Core Duration), the evaluated state is 'Error'.
  • CPU Core Duration - The maximum allowed duration breaching the threshold (seconds).

Next Step

Add or manage Monitor View

Windows Server Monitoring Agent
Resources
Monitoring
Monitor Views