wlmemsmon(1M)wlmemsmon(1M)NAMEwlmemsmon - HP-UX Workload Manager EMS monitor
SYNOPSISDESCRIPTION
The HP-UX Workload Manager (WLM) provides information on how HP-UX WLM
and its managed workloads are performing via the Event Monitoring Ser‐
vice (EMS).
EMS is a monitoring service that polls system resources and sends mes‐
sages when events occur. Events include items such as the loading of a
new HP-UX WLM configuration by or that a particular service-level
objective (SLO) is not being met, or the current value of a metric.
EMS allows you to configure what you consider a noteworthy event, and
receive notification when that event occurs. For more information on
EMS, refer to the ems(5) manpage.
The HP-UX WLM EMS monitor, monitors the HP-UX WLM daemon, and provides
EMS resources that an EMS client can monitor. That information is pro‐
vided to the EMS registrar when a monitoring request has been config‐
ured for a particular resource.
The EMS agent starts and stops You should never start or stop the
process.
provides the following resources. Monitoring of these resources can be
configured using any EMS client, such as the System Administration Man‐
ager (SAM) or the System Management Homepage (SMH), which is an
enhanced version of SAM.
The status of the HP-UX WLM daemon,
The value is either WLM_UP (1) or WLM_DOWN (0).
A character string that displays the time that the current
HP-UX WLM configuration was loaded.
This EMS resource is set only when
keyword is used.
This resource indicates a need for activation of Instant Capac‐
ity reserves when SLOs are failing. (Instant Capacity was for‐
merly known as iCOD.) Possible values are:
(0) - Instant Capacity reserves (formerly known as iCOD reserves)
are not available or no SLOs are failing.
(1) - Instant Capacity reserves (formerly known as iCOD reserves)
exist and, if activated, may reduce the number of SLO failures.
For more information on this resource, see wlmconf(4).
This resource is created for each metric, where met_name
matches the name of the metric as specified in the HP-UX config‐
uration file. This instance identifies a metric's data collec‐
tor as specified with the keyword in the structure. For more
information on specifying the keyword in the configuration file,
refer to the manpage.
This resource is created for each metric, with met_name replaced by
the name of the metric. This instance indicates a specific met‐
ric's smoothing value as specified with the keyword in the
structure. The resource value can range from 0 to 0.999. A
returned value of 0 (the default) signifies that a running aver‐
age is not taken for the data collected; in other words, dips
and spikes of data received by the data collector are not
smoothed out before WLM uses the data. The higher the value, the
more smoothing that is performed. For more information on speci‐
fying the keyword in the configuration file, refer to the man‐
page.
This resource is created for each metric, with met_name replaced by
the name of the metric. This instance indicates whether averag‐
ing is enabled for a specific metric, as specified with the key‐
word in the structure. Possible values are:
(0) - Averaging is disabled, meaning that only the most recent
interval's usage data is used for a metric.
(1) - Averaging is enabled.
For more information on this resource, refer to wlmconf(4).
This resource is created for each metric, with met_name replaced by
the name of the metric. This instance indicates the current
value for a specific metric. In contrast to the preceding metric
resources (which are constant for a given WLM configuration),
the metric_status value is dynamic, meaning that the value
changes periodically during a configuration's deployment.
This resource is created for each SLO, where slo_name
matches the name of the SLO as specified in the HP-UX WLM con‐
figuration file. The resource indicates the priority of the
SLO.
This resource is created for each SLO, with slo_name
replaced by the actual SLO name. The resource indicates the
name of the metric associated with the SLO.
This resource is created for each SLO, with slo_name
replaced by the name of the SLO. The resource indicates the name
of the PRM group associated with the SLO.
This resource is created for each SLO, with slo_name replaced by
the name of the SLO. The resource indicates the status of the
SLO. Possible values for this resource are:
(0) - The SLO is not currently active.
(1) - The SLO is currently passing.
(2) - The SLO is currently failing.
(3) - The SLO is currently failing and is not receiving the full
allocation required to meet this SLO. The SLO's failing can be
caused by a higher priority SLO that has consumed the CPU shares
required by this SLO, or competition with other SLOs at the same
priority.
(4) - The SLO is currently failing and is also receiving the maxi‐
mum CPU allocation specified for this SLO.
(5) - The data collector for this SLO exited unexpectedly. Thus,
the performance of the SLO (passing or failing) is unknown.
(6) - The HP-UX WLM daemon, has not received any data yet from the
data collector for this SLO. (This condition is normal at
startup, and should only persist briefly, until the HP-UX WLM dae‐
mon receives data from the data collector.)
OPTIONS
does not support any command-line options.
RETURN VALUE
returns exit status if no errors occur, and otherwise.
DEPENDENCIES
EMS must be installed to take advantage of
AUTHOR
was developed by HP.
FEEDBACK
If you would like to comment on the current HP-UX WLM functionality or
make suggestions for future releases, please send email to:
wlmfeedback@rsn.hp.com
SEE ALSOwlmd(1M), wlmconf(4), wlm(5), ems(5)
HP-UX Workload Manager User's Guide (/opt/wlm/share/doc/WLMug.pdf)
HP-UX Workload Manager homepage (http://www.hp.com/go/wlm)
wlmemsmon(1M)
