Red Hat NETWORK 4.0 -, Reference Manual

Page: 220 / 290

204 Appendix C. Probes
OK
The probes that have run successfully without error. This is the desired state for all
probes.
Warning
The probes that have crossed their WARNING thresholds.
Critical
The probes that have crossed their CRITICAL thresholds or reached a critical status
by some other means. (Some probes become critical when exceeding their timeout
period.)
While adding probes, select meaningful thresholds that, when crossed, notify you and your
administrators of problems within your infrastructure. Timeout periods are entered in sec-
onds unless otherwise indicated. Exceptions to these rules are noted within the individual
probe references.
Important
Some probes have thresholds based on time. In order for such CRITICAL and WARNING
thresholds 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 instances of
extended 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 time
to establish baseline performance for each of your systems. Although the default values
provided for probes may suit your needs, every organization has a different environment
that may require altering thresholds.
C.2. Apache 1.3.x and 2.0.x
The 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, you
may also use them over secure connections by changing the application protocol to https
and the port to 443 .
C.2.1. Apache::Processes
The Apache::Processes probe monitors the processes executed on an Apache HTTP Server
and collects the following metrics: