3.5.1 Matrix Server Administration Guide

Chapter 13: Configure Service Monitors 226

Timeout: The maximum amount of time that the monitor_agent daemon

will wait for a probe to complete. For most monitors, the default timeout

interval is five seconds. You can use the default setting or specify a new

timeout interval.

Frequency: The interval of time, in seconds, at which the monitor probes

the designated service. You can use the default setting, typically 30

seconds, or enter a new frequency interval.

Script parameters: If you are configuring a HTTP, NIS, or CUSTOM

monitor, this field will ask for the following information. (This field is

unused for the other types of monitors.)

• HTTP service monitor. You will be asked to specify the URL for the

HTTP service. When the monitor performs its probe operation, it will

attempt to retrieve the URL from the server, giving a higher level of

assurance that the service is functioning correctly. If you do not

specify a URL, the probe operation will connect to httpd and wait for a

response. If httpd responds, the monitor assumes that the service is

operating correctly.

• NIS service monitor. You will be asked to set the proto, rpcname,

rpcvers, and domain parameters. Set proto to either udp or tcp,

depending on the protocol used by the NIS protocol version you have

configured. rpcname is typically set to ypserv. Set rpcvers to either 1

or 2 to match the NIS protocol version used by your server. Set

domain to the NIS domain that should be monitored by the NIS

probe.

The rpcinfo command can be useful for determining the correct

values for proto, rpcname, and rpcvers.

• Custom service monitor. You will be asked for the location of the user

probe script. Enter the pathname for the probe script to be used with

the monitor. See “Custom Scripts” on page 270 for information about

writing probe scripts.

When you complete the Add Service Monitor form, the new monitor

appears on the Management Console, as shown in the following example.