Installation guide

Probes
Monitoring-entitled systems can have probes applied to them that constantly confirm their health and full
operability. T his section lists the available probes broken down by command group, such as Apache.
Many probes that monitor internal system aspects (such as the Linux::Disk Usage probe) rather than
external aspects (such as the Network Services::SSH probe) require the installation of the Red Hat
Network monitoring daemon (rhnm d). This requirement is noted within the individual probe reference.
Each probe has its own reference in this section that identifies required fields (marked with *), default
values, and the thresholds that may be set to trigger alerts. Similarly, the beginning of each command
group's section contains information applicable to all probes in that group. Section A.1, “Probe
Guidelines” covers general guidelines; the remaining sections examine individual probes.
Note
Nearly all of the probes use Transmission Control Protocol (T CP) as their transport protocol.
Exceptions to this are noted within the individual probe references.
A.1. Probe Guidelines
The following general guidelines outline the meaning of each probe state, and provide guidance in
setting thresholds for your probes.
The following list provides a brief description of the meaning of each probe state:
Unknown
The probes that cannot collect the metrics needed to determine probe state. Most (though not
all) probes enter this state when exceeding their timeout period. Probes in this state may be
configured incorrectly, as well.
Pending
The probes whose data has not been received by the Red Hat Satellite. It is normal for new
probes to be in this state. However, if all probes move into this state, the monitoring
infrastructure may be failing.
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 CRIT ICAL 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. T imeout periods are entered in seconds unless
Probes
89