216 Appendix C. ProbesOKThe probes that have run successfully without error. This is the desired state for allprobes.WarningThe probes that have crossed their WARNING thresholds.CriticalThe probes that have crossed their CRITICAL thresholds or reached a critical statusby some other means. (Some probes become critical when exceeding their timeoutperiod.)While adding probes, select meaningful thresholds that, when crossed, notify you and youradministrators of problems within your infrastructure. Timeout periods are entered in sec-onds unless otherwise indicated. Exceptions to these rules are noted within the individualprobe references.ImportantSome probes have thresholds based on time. In order for such CRITICAL and WARNINGthresholds to work as intended, their values cannot exceed the amount of time allottedto the timeout period. Otherwise, an UNKNOWN status is returned in all instances ofextended latency, thereby nullifying the thresholds. For this reason, Red Hat strongly rec-ommends ensuring that timeout periods exceed all timed thresholds.Remember that Red Hat recommends running your probes without notifications for a timeto establish baseline performance for each of your systems. Although the default valuesprovided for probes may suit your needs, every organization has a different environmentthat may require altering thresholds.C.2. Apache 1.3.x and 2.0.xThe probes in this section may be applied to instances of the Apache HTTP Server. Al-though the default values presume you will apply these probes using standard HTTP, youmay also use them over secure connections by changing the application protocol to httpsand the port to 443.C.2.1. Apache::ProcessesThe Apache::Processes probe monitors the processes executed on an Apache HTTP Serverand collects the following metrics:
