HP-UX Workload Manager User's Guide

Advanced WLM usage: Using performance metrics
Configuring WLM for metric-based SLOs
Appendix H 477
tune application_procs {
coll_argv = wlmrcvdc glance_prm APP_ACTIVE_PROC sales;
}
As a result of this structure, each time the glance_prm command prints
a value on standard out, wlmrcvdc sends the value to WLM for use in
changing the CPU allocation for the sales group.
For information on other ways to use wlmrcvdc, see wlmrcvdc(1M).
Step 4. Activate the configuration.
# /opt/wlm/bin/wlmd -a config.wlm
substituting your configuration file’s name for config.wlm.
Specifying a data collector
Whenever you use a metric in your WLM configuration, you need to
supply a value for that metric. The coll_argv statement launches a data
collector to gather values for a metric. You can specify a data collector in
a metric-specific tune structure to gather values for that one metric. If
multiple metrics use the same command, such as wlmrcvdc, to collect
values, you can specify the command in a global tune structure, instead
of specifying it separately for each metric in its own metric-specific tune
structure.
The coll_argv keyword is required for SLOs that include a performance
goal. The coll_argv keyword is allowed in global and metric-specific
tune structures.
NOTE Data collectors invoked by WLM run as root and can pose a security
threat. Hewlett-Packard makes no claims of any kind with regard to the
security of data collectors not provided by Hewlett-Packard.
Furthermore, Hewlett-Packard shall not be liable for any security
breaches resulting from the use of said data collectors.
Use the following syntax in a tune structure to specify a data collector
and its command-line arguments:
coll_argv = data_collector_and_arguments;
where