HP-UX Workload Manager User's Guide

Advanced WLM usage: Using performance metrics
Configuring WLM for metric-based SLOs
Appendix H478
data_collector_and_arguments
Is the full path to a data collector, plus any arguments.
Separate arguments with white space. Use double
quotes to form single arguments for an option and
when using characters used in the syntax, such as
semicolons, pound characters (#), and curly brackets.
This string cannot exceed 240 characters.
stdout and stderr for each data collector are sent to /dev/null; however,
you can capture a collector’s stderr output using the coll_stderr
tunable, described in “Capturing your collectors’ stderr (optional)” on
page 479.
Here is an example coll_argv statement:
coll_argv = /opt/finance/bin/fin_mon -freq 3;
WLM provides a built-in data collector called wlmrcvdc. Specify this
collector as follows:
coll_argv = wlmrcvdc [command];
where
command (optional)
Is a command provided for gathering data from
GlancePlus, Oracle, other applications, or for checking
on the status of a Serviceguard package, or a
user-supplied data collector command.
For information on commands available with wlmrcvdc, see “wlmrcvdc”
on page 388.
WLM simplifies the task of developing data collectors with its wlmsend
and wlmrcvdc utilities. For information on these utilities and data
collectors in general, see “Supplying data to WLM” on page 482.
Here is a partial WLM configuration showing the use of wlmrcvdc in a
global tune structure.
# Global wlmrcvdc to collect any metric values sent in via wlmsend:
tune {
coll_argv = wlmrcvdc;
}
# Collector to use instead of the global wlmrcvdc to get values
# for the metric order_transaction_time: