NonStop Cluster Performance Essentials User's Guide, Version 2.2

PROV
BUFFER-DENIALS
10,000
PROV
ITAPI-ERRORS
10,000
PROV
LINUX-ERRORS
10,000
PROV
BFR-BYTES-IN-USE-CURR
10,000
PROV
TOTAL-RECV-MSGS
10,000
PROV
TOTAL-SEND-MSGS
10,000
PROV
QUEUED-COMMANDS
10,000
PROV
FAILED-COMMANDS
10,000
CLIM CPU
CPU Busy
100
CLIM CPU
Memory Used
10,000
CLIM Process
BUSY
100
CLIM Disk
IORATE
10,000
CLIM Disk
Usage
10,000
CLIM Network General
Send Count
10,000
CLIM Network General
Receive Count
10,000
CLIM Network Protocol
TCP Send Count
10,000
CLIM Network Protocol
TCP Receive Count
10,000
CLIM Network Protocol
UDP Send Count
10,000
CLIM Network Protocol
UDP Receive Count
10,000
* Note: For these entities data may be displayed with a five digit negative value.
[Back to TOC]
5.4.2. Alert Logging
Based on where the user creates a threshold, the threshold will retain the scope of
what it encompasses at that time. Alert scope is based on where the user is in the
exploration tree hierarchy when they create the alert. For instance, if the user
creates an alert at the cluster level, this alert will have a global scope, meaning
that the threshold will pertain to all nodes within this cluster that meet the criteria.
The threshold will only be seen at this cluster level when navigating through the
exploration tree, and users will only be able to edit this alert at the cluster level.
Similarly, alerts created at entity-specific levels such as CPU Busy will only be
viewable and editable at this node level and the user will not be able to change the
alert’s scope.
Performance Essentials HP SIM Client and NonStop & Linux Host User Guide – 544813 – 004
57