CPU Monitoring

About CPU Monitoring

CPU monitoring allows you setting CPU thresholds so that you get alerted if your machine’s CPU utilization reaches some critical level preset by you.

Note: for all types of Server/Device monitoring (see Server/Device Monitoring), you need to have Smart Agent downloaded, installed and running on your machine to configure the monitoring (see Downloading Agents and Installing Smart Agent for Windows and Linux).

CPU monitor is a multi-value monitor: it allows you to monitor CPU of all cores on your machine as well as the average across cores.

 

Adding CPU Monitoring

Adding CPU Monitoring for Windows

Go to the Monitors menu, select Server/Device Monitors->CPU and click Add.

http://www.monitis.com/support/wp-content/uploads/2016/06/word-image-5.png

The Add Server/Device Monitor – Step 1 window will open.

Add_CPU_Monitor_step_1-new

If you have already downloaded and installed Smart Agent for Windows, select it from the Agent list.

Make sure that your Smart Agent for Windows is running, as shown under Agent Status. If the Agent is stopped, run it from the Smart Agent Controller window (see Downloading, Installing and Running Smart Agent for Windows).

Agent_Key.png

If you haven’t downloaded Smart Agent for Windows yet, click on the Download Agent button to download it. Follow the instructions under Downloading, Installing and Running Smart Agent for Windows.
Note that it may take up to 5 min for newly installed Agent to appear in the agent list (you can click Refresh to refresh the agent list).

Select the Windows Agent from the list, and click Next.

The Add Server/Device Monitor – Step 2 window will open.

Scr_113.png

Select from the Monitor Group combo box the monitor group for this monitor to be assigned to.

You can also create a new monitor group by clicking on the “+” icon next to Add Group.

You can configure here a threshold of Critical severity level for the new monitor (see Thresholds). You can also edit thresholds of the monitor after it is added in your dashboard.

The threshold you define here applies to all cores.

The number of consecutive checks the threshold condition must be met in order for the monitor to enter Critical state is set to be 1 in the threshold.

Enter the values under the User and Kernel. Your monitor will enter Critical state whenever any of these limits are crossed. You can then assign alert rules to your monitor to start receiving alerts whenever the monitor enters a problem state (see Alert Rules in Alerts 2.0).

To add more Server-Device monitors of different types to the same Smart Agent, click the green “+” button under Add More Monitors (see Adding Multiple Server-Device and Application Monitors for the Same Agent).

Click Add when finished.

The Alert Configuration window will appear.

  • Click Send to All Contacts if you want to send alerts for this monitor to all contacts.
  • Click Custom Configuration (Advanced) to configure sending alerts for this monitor only to selected contacts. The Alert Rules window will open. Click on the Add Alert Rule button to configure alert rule(s) for your monitor.

image008

Set up the alert rule and click Add Rule. See Alert Rules in Alerts 2.0 for more info about alert rules.

Note: To be able to add alert rules, you need to set up thresholds (Critical or Warning) in your monitor first.

A threshold includes two conditions connected by a logical OR. If any of the conditions matches the monitor will enter your specified state.

  • Check fails (response timed out, connection failure, etc)
  • Any or all of your selected metrics meet the failure conditions you specified for them

39.png

Notice that CPU monitor is a multi-value monitor: it allows you to monitor CPU of all cores on your machine, or the average across all CPUs. Just select the objects (CPUs in this case) and/or the average across all objects and then define the metrics expression for them.

40.png

For detailed explanations on how to configure alerting for multi-value monitor see Setting up Alerts for Multi-value Monitors.

  • Click Don’t Send Alerts if you don’t want any alerts for this monitor to be sent.

Your newly created Server-Device monitor will appear in your Monitis dashboard. Wait until it loads the first results.

Scr_115.png

 

Adding CPU Monitoring for Linux

Go to the Monitors menu, select Server/Device Monitors->CPU and click Add.

http://www.monitis.com/support/wp-content/uploads/2016/06/word-image-13.png

The Add Server/Device Monitor – Step 1 window will open.

Add_CPU_Monitor_Step_1_Linux-new

If you have already downloaded and installed Smart Agent for Linux, select it from the Agent list.

Make sure that your Smart Agent for Linux is running, as shown under Agent Status. If the Agent is stopped, run it on your Linux machine (see Downloading, Installing and Running Smart Agent for Linux).

Status Monitoring Smart Agent

If you haven’t downloaded Smart Agent for Linux yet, click on the Download Agent button to download it. Follow the instructions under Downloading, Installing and Running Smart Agent for Linux. Note that it may take up to 5 min for newly installed Agent to appear in the list (you can click Refresh to refresh the agent list).

Select the Linux Agent from the list, and click Next.

The Add Server/Device Monitor – Step 2 window will appear.

Scr_119.png

Select from the Monitor Group combo box the monitor group for this monitor to be assigned to.

You can also create a new monitor group by clicking on the “+” icon next to Add Group.

You can configure here a threshold of Critical severity level for the new monitor (see Thresholds). You can also edit thresholds of the monitor after it is added in your dashboard.

The threshold you define here applies to all cores.

The number of consecutive checks the threshold condition must be met in order for the monitor to enter Critical state is set to be 1 in the threshold.

Enter the values under the Nice, Idle, lowait, User and Kernel. Your monitor will enter Critical state whenever any of these limits are crossed. You can then assign alert rules to your monitor to start receiving alerts whenever the monitor enters a problem state (see Alert Rules in Alerts 2.0).

To add more Server-Device monitors of different types to the same Smart Agent, click the green “+” button under Add More Monitors (see Adding Multiple Server-Device and Application Monitors for the Same Agent).

Click Add when finished.

The Alert Configuration window will appear.

  • Click Send to All Contacts if you want to send alerts for this monitor to all contacts.

Click Custom Configuration (Advanced) to configure sending alerts for this monitor only to selected contacts. The Alert Rules window will open. Click on the Add Alert Rule button to configure alert rule(s) for your monitor.

Scr_87.png

Set up the alert rule and click Add Rule. See Alert Rules in Alerts 2.0 for more info about alert rules.

Note: To be able to add alert rules, you need to set up thresholds (Critical or Warning) in your monitor first.

A threshold includes two conditions connected by a logical OR. If any of the conditions matches the monitor will enter your specified state.

  • Check fails (response timed out, connection failure, etc)
  • Any or all of your selected metrics meet the failure conditions you specified for them

34.png

Notice that CPU monitor is a multi-value monitor: it allows you to monitor CPU of all cores on your machine, or the average across all CPUs. Just select the objects (CPUs in this case) and/or the average across all objects and then define the metrics expression for them.

35.png

For detailed explanations on how to configure alerting for multi-value monitor see Setting up Alerts for Multi-value Monitors.

  • Click Don’t Send Alerts if you don’t want any alerts for this monitor to be sent.

Your newly created Server-Device monitor will appear in your Monitis dashboard. Wait until it will load the first results.

Scr_86.png

 

Viewing CPU Monitor Results

As CPU monitor is a multi-value monitor, you can select any of the CPUs or average across all CPUs to display the metric data for in the chart view of the monitor module.

Scr_84.png

If you switch to the table view, you will be able to see data for all CPUs and the average for every check run.

Scr_83.png

Note: by default check frequency for Server/Device monitors is 5 min. You can upgrade your Server/Device monitors to run on 1 min frequency. See Check Frequency in Server/Device Monitors for more info.