HP-UX Workload Manager User's Guide

Advanced WLM usage: Using performance metrics
Configuring WLM for metric-based SLOs
Appendix H 479
tune order_transaction_time {
coll_argv = /home/orders/data_collector;
}
# Value of metric analysis_application_running given to WLM by wlmsend
# through global wlmrcvdc
slo analysis {
...
condition = metric analysis_application_running;
...
}
# Value of metric job_count given to WLM by wlmsend through
# global wlmrcvdc
slo batch_processing {
...
cpushares = 2 more per metric job_count;
...
}
# Uses metric value given by collector in metric-specific tune structure
slo order_processing {
...
goal = metric order_transaction_time < 10.0;
...
}
If you are using WLM with Serviceguard, you might consider using
wlmrcvdc in a global tune structure with sg_pkg_active to check the
status of all the Serviceguard packages on the current system. For more
information, see “Integrating with Serviceguard” on page 414 or see
sg_pkg_active(1M).
Capturing your collectors’ stderr (optional)
Because they are started by a daemon process, data collectors do not
have a stderr on which to communicate errors. The coll_stderr tunable
allows you to capture these errors. Specify coll_stderr using the
following syntax:
coll_stderr = file;
where