Use this Knowledge Script to monitor system performance. This script maps elements of UNIX performance data using a format similar to Windows Performance Monitor counters. It uses the Object, Counter, and Instance model, and identifies which of those UNIX “counters” you want to monitor. Information for the objects and counters you specify is returned to the management server. The performance data is then stored in the AppManager repository and available for reporting in AppManager charts and reports.
There are several base objects, such as:
UX Disk
UX Virtual Memory
UX Processor
UX Block IO
UX Networking
UX Paging
UX Swapping
Each object has multiple counters and can have multiple instances. You can set both high (Over) and low (Under) thresholds for the counter you are monitoring, and can set up the script to raise an event if the value of the counter you select is greater than the Maximum threshold value, or is less than the Minimum threshold value. You can also specify a consecutive number of times that the over or under threshold value must be crossed before an event is raised.
NOTE:AppManager raises an event only if the counter value is greater than the specified Maximum threshold value or is less than the specified Minimum threshold value. If a counter does not exist on the managed client, the Knowledge Script terminates with an error.
For more information about objects and their counters, see Section 7.0, Counter Reference.
UNIX computer icon
The default interval for this script is Every 10 minutes.
Set the following parameters as needed:
|
Description |
How to Set It |
|---|---|
|
Collect data for current counter value? (y/n) |
Set to y to collect data for charts and reports. If set to y, the script returns the current value of the specified counter. The default is n. |
|
Raise event if maximum threshold is exceeded? (y/n) |
Set to y to raise an event if the counter value is greater than the value specified in as the Maximum threshold parameter. The default is y. |
|
Threshold -- Maximum counter value |
Enter a greater-than threshold for the counter value. If the counter you are monitoring exceeds this value, AppManager raises an event if the Raise event if maximum threshold is exceeded? parameter is enabled. The default is 500. HINT:Keep in mind that the units this value represents (for example, a number, percentage, or rate) depend on the specific counter you are monitoring. |
|
Raise event if minimum threshold is not met? (y/n) |
Set to y to raise an event if the counter value is less than the value specified in the Minimum threshold parameter. The default is y. |
|
Threshold -- Minimum counter value |
Enter a lower-limit threshold for the counter value. If the counter you are monitoring falls below this value, AppManager raises an event if the Raise event when minimum threshold not met? parameter is enabled. The units this value represents depend on the specific counter you are monitoring. The default is 20. |
|
Counter to monitor |
Type the object, counter, and instance(s) to monitor. Use the format object|counter|instance. For example: UX Processor|%System Time|_Total The names are case-sensitive and the delimiter (|) is required. You can enter up to 5 counters, separated by commas and no spaces. Some counters require you to specify an instance name as well as the object and counter. In most cases, if a counter requires an instance name, you can specify the specific instance, for example, a specific CPU or device name, or _Total for all instances. Alternatively, you can leave the instance blank to indicate _Total instances. For example: UX Block IO|Reads/s|,UX Block IO|Writes/s| If instances are not applicable for a counter, you can leave the instance blank. For example: UX Swapping|Swap in KBytes/s| |
|
Consecutive times threshold exceeded |
Enter the number of consecutive times, from 0 to 99, the maximum or minimum threshold should be exceeded before an event is raised. The default is 1 time. |
|
Event severity when maximum threshold exceeded |
Set the event severity level, from 1 to 40, to indicate the importance of the event when the maximum threshold is crossed. The default is 5. |
|
Event severity when minimum threshold not met |
Set the event severity level, from 1 to 40, to indicate the importance of the event when the minimum threshold is crossed. The default is 8. |
|
Event severity when no counter/instance found |
Set the event severity level, from 1 to 40, to indicate the importance of the event when AppManager cannot find a counter or instance. The default is 15. |
|
Event severity for internal failure |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which this job experienced an internal error. The default is 5. |
|
Enable debugging? (y/n) |
Set to y to enable debugging. The default is n. |
Use this Knowledge Script to yield performance information for the counters you are interested in monitoring. It is particularly useful for monitoring system statistics not already covered with other Knowledge Scripts and customizing the monitoring of your UNIX servers. With AppManager, you can use the counter data to start corrective actions when thresholds are crossed, generate more complex and sophisticated graphs, and provide historical information for reporting, trend analysis, and capacity planning.
When specifying counters, use the format object|counter|instance. For example:
UX Processor|%System Time|_Total
Object and counter names are case-sensitive and the delimiter (|) is required. For more information about counters, see Section 7.0, Counter Reference.