| CHECK_INTERVAL | This is the time between checks in seconds. A lower value is more responsive, but is more sensitive to short spikes of high CPU utilization. The default value is 60 seconds. |
| ALARM_THRESHOLD | If the average CPU utilization exceeds this value over any test interval then an alarm will be sent. The default value is 85. |
| NOTIFY_HOW | This setting tells how cpumon will both run and then notify. The possibe values are: syslog, remote_syslog, stderr, stdout, and ito. If stdout or stderr is chosen then cpumon will run in the foreground, otherwise it will background. The default value is stdout. |
| SYSLOG_SERVER | This is a manditory option if the remote_syslog option is used. This is the remote syslog server that you are logging to. (Make sure that the remote server has been started with the -r option so that it will listen externally.) |
| MY_HOSTNAME | This is an optional parameter that is used for ITO messaging. The default is the return value from gethostname() system call. If this is set, then the supplied value will override the one returned from the system. |
| ITO_APP | If ito is chosen as the NOTIFY_HOW value then this can override the default app value of "cpumon". |
| ITO_OBJECT | If ito is chosen as the NOTIFY_HOW value then this can override the default object value of "CPU". |
| ITO_GROUP | This is a mandatory option if ito is chosen as the NOTIFY_HOW value. It is the group that the message belongs to. It has no default value and if cpumon is configured to send messages to ITO, and this is not set then cpumon will not run (at all). |
| CONSISTENT_MESSAGE | Set this to true to insure that the message sent will always be the same. This feature is useful when sending to the ITO console or a syslog, otherwise the message will have unique data in it that may varry from alarm to alarm. |