The CPU load Monitor allows you to analyze the workloads performed by your server and understand what can be done. As a general rule, you want the CPU usage to be as high as possible (for maximum efficiency), but keep the CPU load below one (for minimum delays). This requires analysis of the average and peak values for CPU usage and the CPU load. You have to arrive at a sound judgement of these measurements based on the monitoring data, in order to ensure a high level of performance.

In most cases, while CPU usage is below 100 percent for a certain period, the CPU load will remain less than one for that period, because idle time means that there are no processes waiting in the queue. However, on Linux, processes waiting for disk activity are also included in the system load measurement. In this case, when the processor is not calculating anything, processes can still remain queued while write or read operations are performed. This can be misleading and you have to be aware that on Linux, there can be a long queue of processes, even if CPU usage remains below 100 percent most of the time.
If a client requests your server to be placed in the queue, this will lead to increased response times, which may be critical to your business. As previously noted, in case of a Linux server, if it performs a large number of I/O operations in a distant part of the world with high latency, this can create a queue for other operations that do not require a long time to be executed by the CPU, but are forced to wait, thus leading to severe performance issues. This can be a sign that you need to divide the different types of workloads between different servers.

Note: For all types of local resources monitors, you need to have the Anturis private agent downloaded, installed, and running on your machine, in order to configure monitoring.

Adding a CPU load Monitor

Before proceeding, please ensure that you have created the component and your Anturis Private Agent for Windows/Linux is running.
  1. On the Component page, click Add/Remove Monitors > Add Custom Monitor.
  2. Select the Local Resources Monitors tab and Hardware sub tab view.
  3. Select CPU load and click Next.
  4. Select a period of time from the Monitor Period drop-down menu.
  5. Select the agents (servers) from the list.
  6. Click Next.
  7. Under CPU load threshold, set the appropriate values for an Error threshold and Warning threshold.
  8. Enter a Monitor Name and set consecutive measurements.
  9. Click Next.
  10. On the Monitor test result step, click Next when the test is passed.
  11. Click Finish.

To manage your monitor, click View/Edit parameters.

To add a CPU load monitor via the second option, follow the steps below:
  1. From the Infrastructure view page, click "+" Components.
  2. Select the Server component and click Next.
  3. Select the agent (server) from the list and click Next.
  4. Click Finish.
  5. On the Manage Component Monitors page, select the CPU load slider.
  6. [Optional] Change the monitor Name.
  7. [Optional] Change the default value for refreshing intervals (min).
  8. Enter the appropriate threshold values, under Warning and Error.
  9. Go to Monitor Status Change Rule and specify the number of consecutive measurements needed to change the monitor status.
  10. Click OK.

To manage your monitor, go to the Add/Remove Monitors and click on the slider to deactivate the monitor.


Is this article helpful for you?