Installation guide

This probe confirms it can connect to the HTTP port on the specified host and retrieve the specified
URL. If no URL is specified, the probe will fetch the root document. T he probe looks for a HTTP/1.
message from the system, unless you alter that value. Specifying another port number will override the
default port of 80. Unlike most other probes, this probe will return a CRIT ICAL status if it cannot contact
the system within the timeout period.
This probe supports authentication. Provide a username and password in the appropriate fields to use
this feature. Also, the optional Virtual Host field can be used to monitor a separate documentation set
located on the same physical machine presented as a standalone server. If your Web server is not
configured to use virtual hosts (which is typically the case), you should leave this field blank. If you do
have virtual hosts configured, enter the domain name of the first host here. Add as many probes as
necessary to monitor all virtual hosts on the machine.
Table A.4 7. Network Services::Web Server (HT T P) settings
Field Value
URL Path /
Virtual Host
Expect Header HTTP/1
Expect Content
UserAgent* NOCpulse-check_http/1.0
Username
Password
Timeout* 10
HTTP Port* 80
Critical Maximum Remote Service Latency
Warning Maximum Remote Service Latency
A.9. Oracle 8i, 9i, 10g, and 11g
The probes in this section may be applied to instances of the Oracle database matching the versions
supported. Oracle probes require the configuration of the database and associations made by running
the following command:
$ORACLE_HOME/rdbms/admin/catalog.sql
In addition, for these probes to function properly, the Oracle user configured in the probe must have
minimum privileges of CONNECT and SELECT_CATALOG_ROLE.
Some Oracle probes are specifically aimed at tuning devices for long-term performance gains, rather
than avoiding outages. Therefore, Red Hat recommends scheduling them to occur less frequently,
between every hour and every two days. T his provides a better statistical representation, de-
emphasizing anomalies that can occur at shorter time intervals. This applies to following probes: Buffer
Cache, Data Dictionary Cache, Disk Sort Ratio, Library Cache, and Redo Log.
For CRITICAL and WARNING thresholds based upon time to work as intended, their values cannot
exceed the amount of time allotted to the timeout period. Otherwise, an UNKNOWN status is returned in
all cases of extended latency, thereby nullifying the thresholds. For this reason, Red Hat strongly
recommends ensuring that timeout periods exceed all timed thresholds. In this section, this refers
specifically to the probe T NS Ping.
Red Hat Satellite 5.6 Reference Guide
116