User's Manual

Chapter 7. Monitoring 127
The command above will result in output similar to:
5 ServiceProbe on example4.redhat.com (199.168.36.175 ):
linux:cpu usage
Run as: Unix::CPU.pm --critical=90 --sshhost=199.168.36.175
--warn=70 --timeout=15 --sshuser=nocpulse
--shell=SSHRemoteCommandShell --sshport=4545
Now that you have the ID, you use it with rhn-rhnprobe to examine the probe’s output. Refer to
Section 7.5.2 Viewing the output of rhn-runprobe for instructions.
7.5.2. Viewing the output of rhn-runprobe
Now that you’ve obtained the probe ID with rhn-catalog, you can use it in conjunction with
rhn-runprobe to examine the complete output of the probe. Note that by default, rhn-runprobe
works in test mode, meaning no results are entered in the database. Here are its options:
Option Description
--help List the available options and exit.
--probe=PROBE_ID Run the probe with this ID.
--prob_arg=PARAMETER Override any probe parameters from the database.
--module=PERL_MODULE Package name of alternate code to run.
--log=all=LEVEL Sets log level for a package or package prefix.
--debug=LEVEL Sets numeric debugging level.
--live Executes the probe and both enqueues data and sends out
notifications (if needed).
Table 7-1. rhn-runprobe Options
At a minimum, you should include the --probe and --log options and values. The probe ID satisfies
the former, while the latter should be populated with all to request output from all run levels and the
numeric level of verbosity. Here is an example:
rhn-runprobe --probe=5 --log=all=4
More specifically, you may provide the command parameters derived from rhn-catalog, like so:
rhn-runprobe 5 --log all=4 --sshuser=nocpulse --sshport=4545
This will yield verbose output depicting the probe’s attempted run. Errors are clearly identified.