CPU Utilization Monitor

The SiteScope CPU Utilization Monitor reports the percentage of CPU time that is currently being used on the server. It is important to watch CPU usage on your Web server to ensure that it does not become overloaded on a regular basis.

Each time the CPU Utilization Monitor runs, it returns a status message and writes it in a log file.

Usage Guidelines

What to monitor

When CPU usage becomes too high, clients and customers will either find the system response time has become very slow, or if applications hang as a result of high CPU usage, they simply will not be able to access it. Therefore, it is very important to monitor CPU usage and do something about high usage before it results in outages or poor response times.

Whether the servers in your infrastructure are running with a single CPU or with multiple CPUs, you only need to create one CPU monitor per remote server. If you have multiple CPUs, SiteScope will report on the average usage for all of them.

About scheduling this monitor

In general, the CPU Monitor does not need to be run as often as some of the other monitors. If you do not usually suffer from CPU problems, you can run it less frequently - perhaps every half hour or so. If you are prone to CPU usage problems, you should run it more frequently. All machines will have short spikes of CPU usage, but the primary thing that you are looking for is high usage on a regular basis. This indicates that your system is overloaded and that you need to look for a cause.

Status

The Status reading is the current value returned by this monitor; for example, 68% used. SiteScope displays an average for multiple CPU systems. On NT, this is the average CPU usage between runs of the monitor. On UNIX, this is the instantaneous CPU when the monitor runs.

The status is logged as either OK or warning. A warning status is returned if the CPU is in use more than 90% of the time.

Completing the CPU Utilization Monitor Form

To display the CPU Utilization Monitor form, either click the Edit link for an existing CPU Utilization Monitor in a monitor table, or click the " Add a new Monitor to this group" link on a group's detail page and click the " Add CPU Utilization Monitor link.

Complete the items on the CPU Utilization Monitor form as follows. When all the items are complete, click the Add Monitor button.

Server: Choose the server that you want to monitor. The default is to monitor CPU usage on this server. Click the choose server link to monitor CPU usage on another server.
Update every: Select how often the monitor should check CPU utilization. The default interval is to run or update the monitor once every 10 minutes. Use the drop-down list to the right of the text box to specify another update interval in increments of seconds, minutes, hours, or days. The update interval must be 15 seconds or longer.
Title: Enter a title text for this monitor. This text is displayed in the group detail page, in report titles, and other places in the SiteScope interface. If you do not enter a title text, SiteScope will create a title based on the host, server, or URL being monitored.

Advanced Options

The Advanced Options section presents a number of ways to customize monitor behavior and display. Use this section to customize error and warning thresholds, disable the monitor, set monitor-to-monitor dependencies, customize display options, and enter other monitor specific settings required for special infrastructure environments. The options for this monitor type are described below. Complete the entries as needed and click the Add or Update button to save the settings.

Disable

Check this box to temporarily disable this monitor and any associated alerts. To enable the monitor again, clear the box.

Verify Error

Check this box if you want SiteScope to automatically run this monitor again if it detects an error. When an error is detected, the monitor will immediately be scheduled to run again once.

Note: In order to change the run frequency of this monitor when an error is detected, use the Update every (on errors) option below.

Note: The status returned by the Verify Error run of the monitor will replace the status of the originally scheduled run that detected an error. This may cause the loss of important performance data if the data from the verify run is different than the initial error status.

Warning: Use of this option across many monitor instances may result in significant monitoring delays in the case that multiple monitors are rescheduled to verify errors at the same time.

Update Every (on error)

You use this option to set a new monitoring interval for monitors that have registered an error condition. For example, you may want SiteScope to monitor this item every 10 minutes normally, but as often as every 2 minutes if an error has been detected. Note that this increased scheduling will also affect the number of alerts generated by this monitor.

Schedule

By default, SiteScope monitors are enabled every day of the week. You may, however, schedule your monitors to run only on certain days or on a fixed schedule. Click the Edit schedule link to create or edit a monitor schedule. For more information about working with monitor schedules, see the section on Schedule Preferences for Monitoring.

Monitor Description

Enter additional information about this monitor. The Monitor Description can include HTML tags such as the <BR> <HR>, and <B> tags to control display format and style. The description will appear on the Monitor Detail page.

Report Description

Enter an optional description for this monitor that will make it easier to understand what the monitor does. For example, network traffic or main server response time. This description will be displayed on with each bar chart and graph in Management Reports and appended to the tool-tip displayed when you pass the mouse cursor over the status icon for this monitor on the monitor detail page.

Depends On

To make the running of this monitor dependent on the status of another monitor or monitor group, use the drop-down list to select the monitor on which this monitor is dependent. Select None to remove any dependency.

Depends Condition

If you choose to make the running of this monitor dependent on the status of another monitor, select the status condition that the other monitor or monitor group should have in order for the current monitor to run normally. The current monitor will be run normally as long as the monitor on which it depends reports the condition selected in this option.

List Order

By default, new monitors are listed last on the Monitor Detail page. You may use this drop-down list to choose a different placement for this monitor.

Error if

By default, SiteScope only generates a warning status for the CPU monitor. You may choose to have SiteScope generate an error based on either the total CPU percentage or the percentage of CPU a particular CPU. Use the comparison value and comparison operator list to specify an error threshold such as: >= (greater than or equal to), != (not equal to), or < (less than).

Warning if

By default, SiteScope generates warnings whenever CPU usage goes over 90%, but you can change this to generate a warning based upon a different percentage or an actual amount of CPU in use. Complete this section just as you would for the Error if section, described above.

Good if

SiteScope reports a good status for CPU monitors. You may change this to a specific percentage if you prefer.