Red Hat NETWORK 4.0 -, Справочное руководство

Страница: 184 / 290

168 Chapter 7. Monitoring
The
--commandline
option yields the command parameters set for the probe, while
--dump
retrieves everything else, including alert thresholds and notification intervals and
methods.
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.6.2 Viewing the output of
rhn-runprobe
for instructions.
7.6.2. Viewing the output of
rhn-runprobe
Now that you have obtained the probe ID with
rhn-catalog
, 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
Set log level for a package or package prefix.
--debug= LEVEL
Set numeric debugging level.
--live
Execute the probe, enqueue data and send out
notifications (if needed).
Table 7-1.
rhn-runprobe
Options
At a minimum, you should include the
--probe
option, the
--log
option, and values
for each. The
--probe
option takes the probeID as its value and the
--log
option takes
the value "all" (for all run levels) and a numeric verbosity level as its values. Here is an
example:
rhn-runprobe --probe=5 --log=all=4