Appendix C. Probes
159
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.
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
Table C-47. Network Services::Web Server (HTTP) settings
C.9. Oracle 8i and 9i
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 run-
ning:
$ORACLE_HOME/rdbms/admin/catalog.sql
In addition, for these probes to function prop-
erly, the Oracle user configured in the probe must have minimum privileges of CONNECT and SE-
LECT_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. This will provide a better statistical representation than every
few minutes while de-emphasizing anomalies that can occur. 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 will be
returned in all cases of extended latency, thereby nullifying the thresholds. For this reason, Red Hat
strongly recommends ensuring timeout periods exceed all timed thresholds. In this section, this refers
specifically to the probe TNS Ping.
Finally, customers using these Oracle probes against a database using Oracle’s Multi-Threaded Server
(MTS) will need to contact Red Hat support to have entries added to the RHN Server’s /etc/hosts file
to ensure the DNS name is resolved correctly.
Содержание NETWORK 3.6 -
Страница 1: ...Red Hat Network 3 6 Reference Guide ...
Страница 8: ......
Страница 54: ...42 Chapter 4 Red Hat Network Alert Notification Tool ...
Страница 68: ...56 Chapter 5 Red Hat Network Registration Client ...
Страница 130: ...118 Chapter 6 Red Hat Network Website ...
Страница 138: ...126 Appendix A Command Line Config Management Tools ...
Страница 142: ...130 Appendix B RHN API Access ...
Страница 186: ...174 Appendix C Probes ...
Страница 192: ...180 Glossary ...