203
Appendix C. Probes
As described in
Section 6.10, “Monitoring —
”
, Monitoring-entitled systems can have probes applied to them that constantly confirm their health
and full operability. This appendix 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 (
rhnmd
). This requirement is noted within the individual probe reference.
Each probe has its own reference in this appendix 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 C.1,
“Probe Guidelines”
covers general guidelines; the remaining sections examine individual probes.
Note
Nearly all of the probes use
Transmission Control Protocol
(TCP) as their transport
protocol. Exceptions to this are noted within the individual probe references.
C.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 RHN Satellite Server. It is normal for new
probes to be in this state. However, if all probes move into this state, your 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 CRITICAL thresholds or reached a critical status by some
other means. (Some probes become critical when exceeding their timeout period.)
Содержание NETWORK SATELLITE 5.2 - CHANNEL MANAGEMENT
Страница 1: ...Red Hat Network Satellite 5 2 Reference Guide Red Hat Network Satellite ...
Страница 2: ...Reference Guide Red Hat Network Satellite 5 2 Reference Guide Red Hat Network Satellite Edition 5 2 ...
Страница 10: ...x ...
Страница 30: ...Chapter 2 Red Hat Update Agent 18 Figure 2 11 Available Package Updates ...
Страница 46: ...34 ...
Страница 68: ...56 ...
Страница 162: ...150 ...
Страница 174: ...162 ...
Страница 186: ...174 ...
Страница 259: ...247 Appendix D Revision History Revision History Revision 1 0 ...
Страница 260: ...248 ...
Страница 268: ...256 ...