240 Appendix C. ProbesField ValueURL Path /Virtual HostExpect Header HTTP/1Expect ContentUserAgent* NOCpulse-check_http/1.0UsernamePasswordTimeout* 10HTTP Port* 80Critical Maximum Remote Service LatencyWarning Maximum Remote Service LatencyTable C-47. Network Services::Web Server (HTTP) settingsC.9. Oracle 8i and 9iThe probes in this section may be applied to instances of the Oracle database matching theversions supported. Oracle probes require the configuration of the database and associa-tions made by running the following command:$ORACLE_HOME/rdbms/admin/catalog.sqlIn addition, for these probes to function properly, the Oracle user configured in the probemust have minimum privileges of CONNECT and SELECT_CATALOG_ROLE.Some Oracle probes are specifically aimed at tuning devices for long-term performancegains, rather than avoiding outages. Therefore, Red Hat recommends scheduling them tooccur less frequently, between every hour and every two days. This provides a better sta-tistical 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, theirvalues cannot exceed the amount of time allotted to the timeout period. Otherwise, an UN-KNOWN status is returned in all cases of extended latency, thereby nullifying the thresh-olds. For this reason, Red Hat strongly recommends ensuring that timeout periods exceedall timed thresholds. In this section, this refers specifically to the probe TNS Ping.
