HP-UX Workload Manager User's Guide

Advanced WLM usage: Using performance metrics
Supplying data to WLM
Appendix H486
tune metricNC {
coll_argv = collector_path collector_args ;
}
wlmrcvdc is an example of a native collector.
What happens when there is no new data?
If an entire WLM interval passes and WLM does not receive any new
data for a metric, all controllers using that metric simply request the
same allocations for their associated workload groups as they did the
previous interval. As always, the requests may not be met due to the
CPU resource requests of other controllers.
NOTE The current WLM interval length is available through the WLM_INTERVAL
environment variable to data collectors started by WLM (by specifying
the data collector in a coll_argv statement in a WLM configuration
file).
I have this type of data—how do I send it to WLM?
This section focuses on the type of data you have collected or plan to
collect. Knowing the type of data, you can then determine the best way to
get that data to WLM.
If you have any of the following types of data, send the data to WLM as
explained in this section:
• ARM transaction data
• GlancePlus application data
• GlancePlus global data
• GlancePlus PRM-specific application data
• GlancePlus PRM-controlled volume group data
• Oracle database data
• Existing metrics