Red Hat NETWORK SATELLITE 5.1.1 Reference Manual page 149

Probe Status —
In these tables, clicking the name of the system takes you to the Probes tab of the System Details
page. Clicking the name of the probe takes you to its Current State page. From there, you may edit
the probe, delete it, and generate reports based upon its results.
Monitoring data and probe status information that was previously availble only through the web
interface of the Satellite can now be exported as a CSV file. Click on the Download CSV links
throughout the Monitoring pages to download CSV files of relevent information. The exported data
may include, but is not limited to:
• Probe status
• All probes in a given state (OK, WARN, UNKNOWN, CRITICAL, PENDING)
• A Probe Event history
6.10.1.1. Probe Status
The probes that have crossed their CRITICAL thresholds or reached a critical status by some other
means. For instance, some probes become critical (rather than unknown) when exceeding their
timeout period.
6.10.1.2. Probe Status
The probes that have crossed their WARNING thresholds.
6.10.1.3. Probe Status
The probes that cannot collect the metrics needed to determine probe state. Most but not all probes
enter an unknown state when exceeding their timeout period. This may mean that the timeout period
should be increased, or the connection cannot be established to the monitored system.
It is also possible the probes' configuration parameters are not correct and their data cannot be found.
Finally, this state may indicate that a software error has occurred.
6.10.1.4. Probe Status
The probes whose data have not been received by RHN. This state is expected for a probe that
has just been scheduled but has not yet run. If all probes go into a pending state, your monitoring
infrastructure may be failing.
6.10.1.5. Probe Status
The probes that have run successfully without exception. This is the state desired for all probes.
Critical —
Warning —
Unknown —
Pending —
OK —
137