|
Oracle® Enterprise Manager Metric Reference Manual
10g Release 1 (10.1) Part No. B12015-01 |
|
|
|
|
The host metrics provide description, data source, metric index (where applicable), and user action information for each metric.
This metric provides data on aggregate resource usage on a per project basis.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent Waiting for CPU over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent sleeping in Data Page Faults over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of Major Page Faults engendered by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of Minor Page Faults engendered by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of character I/O bytes Read and Written by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of blocks Read by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of blocks Written by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of Involuntary Context Switches made by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of Messages Received by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of Messages Sent by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of Signals taken by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of system calls made by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of Voluntary Context Switches made by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent sleeping on User Lock Waits over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent sleeping in all other ways over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent Stopped over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of swap operations engendered by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent in System mode over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent sleeping in System Page Faults over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent in System Traps over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent sleeping in Text Page Faults over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent in User mode over its lifetime.
This metric is available only on Solaris version 9 and later.
The number of processes owned by the project measured in the aggregate.
This metric is available only on Solaris version 9 and later.
The percent CPU time used by the process.
This metric is available only on Solaris version 9 and later.
The ratio of the process resident set size to physical memory.
This metric is available only on Solaris version 9 and later.
The total number of KiloBytes of memory consumed by the process heap at the time that it is sampled.
This metric is available only on Solaris version 9 and later.
The resident set size of the process in kilobytes.
This metric is available only on Solaris version 9 and later.
The size of the process virtual address space in kilobytes.
This metric is available only on Solaris version 9 and later.
The metric indicates whether the host is reachable or not. A host could be unreachable due to various reasons. The network is down or the Management Agent on the host is down (which could be because the host itself is shutdown).
The number of threads active in the current Process.
This metric is available only on Solaris version 9 and later.
This metric provides data on aggregate resource usage on a per user basis.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent Waiting for CPU over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent sleeping in Data Page Faults over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of Major Page Faults engendered by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of Minor Page Faults engendered by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of character I/O bytes Read and Written by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of blocks Read by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of blocks Written by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of Involuntary Context Switches made by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of Messages Received by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of Messages Sent by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of Signals taken by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of system calls made by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of Voluntary Context Switches made by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent Stopped over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of Swap Operations engendered by the process over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent in System mode over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent sleeping in System Page Faults over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent in System Traps over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent sleeping in Text Page Faults over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent sleeping on User Lock Waits over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent in User mode over its lifetime.
This metric is available only on Solaris version 9 and later.
The cumulative number of seconds that this process has spent sleeping in all other ways over its lifetime.
This metric is available only on Solaris version 9 and later.
The number of processes owned by the user measured in the aggregate.
This metric is available only on Solaris version 9 and later.
The number of threads active in the current Process.
This metric is available only on Solaris version 9 and later.
The percent CPU time used by the process.
This metric is available only on Solaris version 9 and later.
The ratio of the process resident set size to physical memory.
This metric is available only on Solaris version 9 and later.
The total number of kilobytes of memory consumed by the process heap at the time that it is sampled.
This metric is available only on Solaris version 9 and later.
The resident set size of the process in kilobytes.
This metric is available only on Solaris version 9 and later.
The size of the process virtual address space in kilobytes.
This metric is available only on Solaris version 9 and later.
The Buffer Activity metric provides information about OS memory buffer usage. This metric reports buffer activity for transfers, accesses, and cache (kernel block buffer cache) hit ratios per second.
The data sources for this metric category include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
Represents the number of reads from block devices to buffer cache as a percentage of all buffer reads.
Represents the number of reads performed on the buffer cache per second.
Represents the number of writes from block devices to buffer cache as a percentage of all buffer writes.
Represents the number of writes performed on the buffer cache per second.
Represents the number of reads per second from character devices using physical I/O mechanisms.
Represents the number of writes per second from character devices using physical I/O mechanisms.
Represents the number of reads performed per second from block devices to the system buffer cache.
Represents the number of physical writes from block devices to the system buffer cache.
The CPU Usage metric provides information about the percentage of time the CPU was in various states, for example, idle state and wait state. The metric also provides information about the percentage of CPU time spent in user and system mode. All data is per-CPU in a multi-CPU system.
On HP Tru64, this information is available as the cumulative total for all the CPUs and not for each CPU which is monitored in the Load metric. Hence, this metric is not available on HP Tru64.
The data sources for this metric category include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics (class cpu_stat) |
| HP | pstat_getprocessor() system call |
| Linux | /proc/stat |
| HP Tru64 | not available |
| IBM AIX | oracle_kstat() system call |
| Windows | performance data counters |
Represents the percentage of time that the CPU was idle and the system did not have an outstanding disk I/O request. This metric checks the percentage of processor time in idle mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
Represents the percentage of time that the CPU receives and services hardware interruptions during representative intervals. This metric checks the percentage of processor time in interrupt mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).
This metric is available only on Windows.
Represents the percentage of time that the CPU is running in system mode (kernel). This metric checks the percentage of processor time in system mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
Represents the portion of processor time running in user mode. This metric checks the percentage of processor time in user mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
Represents the percentage of time that the CPU was idle during which the system had an outstanding disk I/O request. This metric checks the percentage of processor time in wait mode for the CPU(s) specified by the Host CPU parameter, such as cpu_stat0, CPU0, or * (for all CPUs on the system).
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
The Disk Activity metric monitors the hard disk activity on the target being monitored. For each device on the system, this metric provides information about access to the device. This information includes: device name, disk utilization, write statistics, and read statistics for the device.
The data sources for this metric category include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics (class kstat_io) |
| HP | sar command |
| Linux | iostat command |
| HP Tru64 | table() system call |
| IBM AIX | oracle_kstat() system call |
| Windows | performance data counters |
Represents the sum of average wait time and average run time.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-1 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 15 Minutes | After Every Sample | > | Not Defined | Not Defined | 6 | Average service time for disk %keyvalue% is %value% ms |
For this metric you can set different warning and critical threshold values for each "Disk Device" object.
If warning or critical threshold values are currently set for any "Disk Device" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Disk Device" object, use the Edit Thresholds page. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
Represents the average time spent by the command waiting on the queue for getting executed.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-2 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 15 Minutes | After Every Sample | > | Not Defined | Not Defined | 6 | Average wait time for disk %keyvalue% is %value% ms |
For this metric you can set different warning and critical threshold values for each "Disk Device" object.
If warning or critical threshold values are currently set for any "Disk Device" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Disk Device" object, use the Edit Thresholds page. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
Represents the average number of commands waiting for service (queue length).
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
Represents the average time spent by the command on the active queue waiting for its execution to be completed.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
Represents the number of blocks (512 bytes) written per second.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
Represents the number of blocks (512 bytes) read per second.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
Represents the disk reads per second for the specified disk device.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
Represents the amount of disk space utilization as a percentage of capacity.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-3 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 15 Minutes | After Every Sample | > | 80 | 95 | 6 | Disk Utilization for %keyValue% is %value%%% |
For this metric you can set different warning and critical threshold values for each "Disk Device" object.
If warning or critical threshold values are currently set for any "Disk Device" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Disk Device" object, use the Edit Thresholds page. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
Represents the disk writes per second for the specified disk device.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
The Disk Device Errors metric provides the number of errors on the disk device.
This metric is available only Solaris.
Represents the error count of hard errors encountered while accessing the disk. Hard errors are considered serious and may be traced to misconfigured or bad disk devices.
This metric is available only on Solaris.
Represents the error count of soft errors encountered while accessing the disk. Soft errors are synonymous to warnings.
This metric is available only on Solaris.
Represents the sum of all errors on the particular device.
This metric is available only on Solaris.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 72 Hours |
Represents the error count of network errors encountered. This generally indicates a problem with the network layer.
This metric is available only on Solaris.
The File Access System Calls metric provides information about the usage of file access system calls.
Represents the number of file system blocks read per second performing direct lookup.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | not available |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of lookuppn() calls made over this five-second period divided by five.
Represents the number of system iget() calls made per second. iget is a file access system routine.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel memory structure (class cpu_vminfo) |
| HP | sar command |
| Linux | not available |
| HP Tru64 | not available |
| IBM AIX | kernel memory structure (class cpu_vminfo) |
| Windows | not available |
This data is obtained using the OS sar command, which is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of iget() calls made over this five-second period divided by five.
Represents the number of file system lookuppn() (pathname translation) calls made per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | not available |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of lookuppn() calls made over this five-second period divided by five.
The Filesystems metrics provide information about local file systems on the computer.
Represents the name of the disk device resource.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
Represents the total space (in megabytes) allocated in the file system.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
Represents the percentage of total space allocated in the file system.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-4 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 15 Minutes | After Every 24 Samples | <
|
20 | 5 | 1 | Filesystem %keyValue% has only %value%%% available space |
For this metric you can set different warning and critical threshold values for each "Mount Point" object.
If warning or critical threshold values are currently set for any "Mount Point" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Mount Point" object, use the Edit Thresholds page. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
The Inventory metric is used for periodic collection of host configuration information. By default, host configuration is collected every 24 hours.
The Kernel Memory metric provides information on kernel memory allocation (KMA) activities.
This metric is implemented only on Solaris.
This metric represents the number of requests for large memory that failed, that is, requests that were not satisfied.
This metric is implemented only on Solaris.
This metric represents the number of oversized requests made that could not be satisfied. Oversized memory requests are allocated dynamically so there is no pool for such requests.
This metric is implemented only on Solaris.
This metric represents the number of requests for small memory that failed, that is, requests that were not satisfied.
This metric is implemented only on Solaris.
This metric represents the amount of memory, in bytes, the kernel memory allocation (KMA) has for the large pool; the pool used for allocating and reserving large memory requests.
This metric is implemented only on Solaris.
This metric represents the amount of memory allocated for oversized memory requests.
This metric is implemented only on Solaris.
This metric represents the amount of memory, in bytes, the Kernel Memory Allocation has for the small pool; the pool used for allocating and reserving small memory requests.
This metric is implemented only on Solaris.
This metric represents the amount of memory, in bytes, the kernel allocated to satisfy large memory requests.
This metric is implemented only on Solaris.
This metric represents the amount of memory, in bytes, the kernel allocated to satisfy small memory requests.
This metric is implemented only on Solaris.
The Load metric provides information about the number of runnable processes on the system run queue. If this is greater than the number of CPU's on the system, then excess load exists.
The data sources for this metric category include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | performance data counters |
Represents the average number of jobs waiting for I/O in the last interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-5 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 5 Minutes | After Every Sample | > | 40 | 80 | 6 | CPU I/O Wait is %value%%% |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | performance data counters |
A high percentage of I/O wait can indicate a hardware problem, a slow NFS server, or poor load-balancing among local file systems and disks. Check the system messages log for any hardware errors. Use the iostat -xn command or the nfsstat -c (NFS client-side statistics) command or both to determine which disks or file systems are slow to respond. Check to see if the problem is with one or more swap partitions, as lack of swap or poor disk load balancing can cause these to become overloaded. Depending on the specific problem, fixes may include: NFS client or server tuning, hardware replacement, moving applications to other file systems, adding swap space, or restructuring a file system for better performance.
For UNIX-based platforms, this metric represents the amount of CPU being used in SYSTEM mode as a percentage of total CPU processing power.
For Windows, this metric represents the percentage of time the process threads spent executing code in privileged mode.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | performance data counters |
For UNIX-based platforms, this metric represents the amount of CPU being used in USER mode as a percentage of total CPU processing power.
For Windows, this metric represents the percentage of time the processor spends in the user mode. This metric displays the average busy time as a percentage of the sample time.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | performance data counters |
Represents the percentage of time the processor spends receiving and servicing hardware interrupts during sample intervals. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards, and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended during interrupts. Most system clocks interrupt the processor every 10 milliseconds, creating a background of interrupt activity. Suspends normal thread execution during interrupts.
This metric is available only on Windows.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-6 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every Minute | After Every Sample | > | 40 | 80 | 6 | CPU % Interrupt Time is %value%%% |
Processor Queue Length is the number of ready threads in the processor queue. There is a single queue for processor time even on computers with multiple processors. A sustained processor queue of less than 10 threads per processor is normally acceptable, dependent on the workload.
This metric is available only on Windows.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-7 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every Minute | After Every Sample | > | 10 | 20 | 6 | CPU Queue Length is %value% |
For UNIX-based platforms, this metric represents the amount of CPU utilization as a percentage of total CPU processing power available.
For Windows, this metric represents the percentage of time the CPU spends to execute a non-Idle thread. CPU Utilization (%) is the primary indicator of processor activity.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-8 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 5 Minutes | After Every Sample | > | 80 | 95 | 6 | CPU Utilization is %value%%% |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | performance data counters |
Represents the amount of free memory as a percentage of total memory.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | Windows API |
Represents the maximum of the average service time of all disks. Units are represented in milliseconds.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | not available |
For UNIX-based systems, this metric represents the number of pages per second scanned by the page stealing daemon.
For Windows, this metric represents the rate at which pages are read from or written to disk to resolve hard page faults. The metric is a primary indicator of the kinds of faults that cause system-wide delays.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-9 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 5 Minutes | After Every Sample | > | Not Defined | Not Defined | 6 | Page scan rate is %value% /sec |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | performance data counters |
Represents the amount of free memory as a percentage of total memory.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-10 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 5 Minutes | After Every Sample | > | 99 | Not Defined | 6 | Memory Utilization is %value%%% |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | Windows API |
Indicates the rate at which pages are read from or written to disk to resolve hard page faults. It is a primary indicator of the kinds of faults that cause systemwide delays. It is counted in numbers of pages. It includes pages retrieved to satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.
This metric is available only on Windows.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-11 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every Minute | After Every Sample | > | Not Defined | Not Defined | 6 | Page transfers rate is %value% /sec |
Represents the average number of processes in memory and subject to be run in the last interval. This metric checks the run queue.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | not available |
Check the load on the system using the UNIX uptime or top commands. Also, check for processes using too much CPU time by using the top and ps -ef commands. Note that the issue may be a large number of instances of one or more processes, rather than a few processes each taking up a large amount of CPU time. Kill processes using excessive CPU time.
Represents the average number of processes in memory and subject to be run in the last interval. This metric checks the run queue.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | not available |
Check the load on the system using the UNIX uptime or top commands. Also, check for processes using too much CPU time by using the top and ps -ef commands. Note that the issue may be a large number of instances of one or more processes, rather than a few processes each taking up a large amount of CPU time. Kill processes using excessive CPU time.
Represents the average number of processes in memory and subject to be run in the last interval. This metric checks the run queue.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-12 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 5 Minutes | After Every Sample | > | 10 | 20 | 6 | CPU Load is %value% |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | not available |
Check the load on the system using the UNIX uptime or top commands. Also, check for processes using too much CPU time by using the top and ps -ef commands. Note that the issue may be a large number of instances of one or more processes, rather than a few processes each taking up a large amount of CPU time. Kill processes using excessive CPU time.
For UNIX-based platforms, this metric represents the percentage of swapped memory in use for the last interval.
For Windows, this metric represents the percentage of page file instance used.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-13 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 5 Minutes | After Every Sample | > | 80 | 95 | 6 | Swap Utilization is %value%%% |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | Windows API and Performance data counters |
For UNIX-based platforms, check the swap usage using the UNIX top command or the Solaris swap -l command. Additional swap can be added to an existing file system by creating a swap file and then adding the file to the system swap pool. (See documentation for your UNIX OS). If swap is mounted on /tmp, space can be freed by removing any junk files in /tmp. If it is not possible to add file system swap or free up enough space, additional swap will have to be added by adding a raw disk partition to the swap pool. See UNIX documentation for procedures.
For Windows, check the page file usage and add an additional page file if current limits are insufficient.
Represents the rate of I/O (read and write) operations, calculated from all disks.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | not available |
Represents the total number of processes currently running on the system. This metric checks the number of processes running on the system.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | performance data counters |
Total amount of page file space available to be allocated by processes. Paging files are shared by all processes and the lack of space in paging files can prevent processes from allocating memory.
This metric is available only on Windows.
Represents the total number of users currently logged into the system. This metric checks the number of users running on the system.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics |
| HP | pstat_getdynamic(), pstat_getprocessor(), pstat_getproc(), pstat_getstatic(), getutent(), pstat_getvminfo() system calls |
| Linux | uptime, free, getconf, ps, iostat, sar, w OS commands; /proc/stat |
| HP Tru64 | table() system call, uptime, vmstat, psrinfo, ps, who, swapon OS commands |
| IBM AIX | oracle_kstat(), getutent(), getproc(), sysconf() system calls |
| Windows | not available |
The Message and Semaphore Activity metric provides information about the message and semaphore activity of the host system being monitored.
Represents the number of msgrcv system calls made per second. The msgrcv system call reads a message from one queue to another user-defined queue.
Represents the number of semop system calls made per second. The semop system call is used to perform semaphore operations on a set of semaphores.
The Network Interfaces metric includes input errors and interface collisions on the network interface. The following network interfaces are supported: le, hme, qfe, ge, and fddi.
The data sources for this metric category include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel memory structures (kstat) |
| HP | netstat, lanscan, and lanadmin commands |
| Linux | netstat command and /proc/net/dev |
| HP Tru64 | netstat command |
| IBM AIX | oracle_kstat() system call |
| Windows | not available |
Represents the number of input errors, per second, encountered on the device for unsuccessful reception due to hardware/network errors. This metric checks the rate of input errors on the network interface specified by the network device names parameter, such as le0 or * (for all network interfaces).
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Represents the number of collisions per second. This metric checks the rate of collisions on the network interface specified by the network device names parameter, such as le0 or * (for all network interfaces).
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Represents the percentage of network bandwidth being used by reading and writing from and to the network for full-duplex network connections.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-14 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 5 Minutes | After Every Sample | > | Not Defined | Not Defined | 6 | Network utilization for %keyvalue% is %value%%% |
For this metric you can set different warning and critical threshold values for each "Network Interface Name" object.
If warning or critical threshold values are currently set for any "Network Interface Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Network Interface Name" object, use the Edit Thresholds page. See the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
Represents the number of output errors per second. This metric checks the rate of output errors on the network interface specified by the network device names parameter, such as le0 or * (for all network interfaces).
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Represents the amount of megabytes per second read from the specific interface.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Represents the amount of network bandwidth being used for reading from the network as a percentage of total read capacity.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Represents the amount of megabytes per second written to the specific interface.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Represents the amount of network bandwidth being used for writing to the network as a percentage of total read capacity.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
The Paging Activity metric provides the amount of paging activity on the system.
The data sources for this metric category include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics (class misc cpu_stat) |
| HP | pstat_getvminfo() system call |
| Linux | sar command |
| HP Tru64 | table() system call and vmstat command |
| IBM AIX | oracle_kstat() system call |
| Windows | performance data counters |
Represents the minor page faults by way of hat_fault() per second. This metric checks the number of faults for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
Cache Faults/sec is the rate at which faults occur when a page sought in the file system cache is not found and must be retrieved from elsewhere in memory (a soft fault) or from disk (a hard fault). The file system cache is an area of physical memory that stores recently used pages of data for applications. Cache activity is a reliable indicator of most application I/O operations. This metric shows the number of faults, without regard for the number of pages faulted in each operation.
This metric is available only on Windows.
Copy-on-Write faults/sec is the rate at which page faults are caused by attempts to write that have been satisfied by coping of the page from elsewhere in physical memory. This is an economical way of sharing data since pages are only copied when they are written to; otherwise, the page is shared. This metric shows the number of copies, without regard for the number of pages copied in each operation.
This metric is available only on Windows.
Demand Zero Faults/sec is the rate at which a zeroed page is required to satisfy the fault. Zeroed pages, pages emptied of previously stored data and filled with zeros, are a security feature of Windows that prevent processes from seeing data stored by earlier processes that used the memory space. Windows maintains a list of zeroed pages to accelerate this process. This metric shows the number of faults, without regard to the number of pages retrieved to satisfy the fault.
This metric is available only on Windows.
Represents the percentage of UFS inodes taken off the freelist by iget which had reusable pages associated with them. These pages are flushed and cannot be reclaimed by processes.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
Page Faults/sec is the average number of pages faulted per second. It is measured in number of pages faulted per second because only one page is faulted in each fault operation, hence this is also equal to the number of page fault operations. This metric includes both hard faults (those that require disk access) and soft faults (where the faulted page is found elsewhere in physical memory.) Most processors can handle large numbers of soft faults without significant consequence. However, hard faults, which require disk access, can cause significant delays.
This metric is available only on Windows.
Represents the number of protection faults per second. These faults occur when a program attempts to access memory it should not access, receives a segmentation violation signal, and dumps a core file. This metric checks the number of faults for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
For UNIX-based systems, represents the number of page read ins per second (read from disk to resolve fault memory references) by the virtual memory manager. Along with Page Outs, this statistic represents the amount of real I/O initiated by the virtual memory manager. This metric checks the number of page read ins for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).
For Windows, this metric is the rate at which the disk was read to resolve hard page faults. It shows the number of reads operations, without regard to the number of pages retrieved in each operation. Hard page faults occur when a process references a page in virtual memory that is not in working set or elsewhere in physical memory, and must be retrieved from disk. This metric is a primary indicator of the kinds of faults that cause systemwide delays. It includes read operations to satisfy faults in the file system cache (usually requested by applications) and in non-cached mapped memory files.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics (class misc cpu_stat) |
| HP | pstat_getvminfo() system call |
| Linux | not available |
| HP Tru64 | table() system call and vmstat command |
| IBM AIX | oracle_kstat() system call |
| Windows | performance data counters |
For UNIX-based systems, represents the number of page write outs to disk per second. This metric checks the number of page write outs for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).
For Windows, this metric is the rate at which pages are written to disk to free up space in physical memory. Pages are written to disk only if they are changed while in physical memory, so they are likely to hold data, not code. This metric shows write operations, without regard to the number of pages written in each operation.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
For UNIX-based systems, represents the number of pages paged in (read from disk to resolve fault memory references) per second. This metric checks the number of pages paged in for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).
For Windows, this metric is the rate at which pages are read from disk to resolve hard page faults. Hard page faults occur when a process refers to a page in virtual memory that is not in its working set or elsewhere in physical memory, and must be retrieved from disk. When a page is faulted, the system tries to read multiple contiguous pages into memory to maximize the benefit of the read operation.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics (class misc cpu_stat) |
| HP | pstat_getvminfo() system call |
| Linux | sar command |
| HP Tru64 | table() system call and vmstat command |
| IBM AIX | oracle_kstat() system call |
| Windows | performance data counters |
For UNIX-based systems, represents the number of pages written out (per second) by the virtual memory manager. Along with Page Outs, this statistic represents the amount of real I/O initiated by the virtual memory manager. This metric checks the number of pages paged out for the CPU(s) specified by the Host CPU(s) parameter, such as cpu_stat0 or * (for all CPUs on the system).
For Windows, this metric is the rate at which pages are written to disk to free up space in physical memory. Pages are written back to disk only if they are changed in physical memory, so they are likely to hold data, not code. A high rate of pages output might indicate a memory shortage. Windows writes more pages back to disk to free up space when physical memory is in short supply.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
Represents the number of pages that are determined unused, by the pageout daemon (also called the page stealing daemon), and put on the list of free pages.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics (class misc cpu_stat) |
| HP | pstat_getvminfo() system call |
| Linux | not available |
| HP Tru64 | table() system call and vmstat command |
| IBM AIX | oracle_kstat() system call |
| Windows | not available |
Represents the scan rate is the number of pages per second scanned by the page stealing daemon.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 15 Minutes |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | kernel statistics (class misc cpu_stat) |
| HP | pstat_getvminfo() system call |
| Linux | not available |
| HP Tru64 | table() system call and vmstat command |
| IBM AIX | oracle_kstat() system call |
| Windows | not available |
Transition Faults/sec is the rate at which page faults are resolved by recovering pages that were being used by another process sharing the page, or were on the modified page list or the standby list, or were being written to disk at the time of the page fault. The pages were recovered without additional disk activity. Transition faults are counted in numbers of faults; because only one page is faulted in each operation, it is also equal to the number of pages faulted.
This metric is available only on Windows.
The Process, Inode, File Tables Stats metric provides information about the process, inode, and file tables status.
The data sources for this metric category include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | sar command |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
Represents the number of times the system file table overflowed, that is, the number of times that the OS could not find any available entries in the table in the sampling period chosen to collect the data.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | sar command |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.
Represents the number of times the inode table overflowed, that is, the number of times the OS could not find any available inode table entries.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | not available |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.
Represents the maximum size of the inode table.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | sar command |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.
Represents the maximum size of the process table.
Data for this column is not available on Linux.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling once in a five-second interval.
Represents the maximum size of the system file table.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | sar command |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.
Represents the number of times the process table overflowed, that is, the number of times the OS could not find any process table entries in a five-second interval.
Represents the current size of the inode table.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | sar command |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.
Represents the current size of the process table.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | sar command |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling once in a five-second interval.
Represents the current size of the system file table.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | sar command |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.
The Swap Area Status metric provides the status of the swap memory on the system.
The data sources for this metric category include the following:
| Host | Data Source |
|---|---|
| Solaris | swap |
| HP | swapinfo |
| Linux | /proc/swaps |
| HP Tru64 | swapon |
| IBM AIX | lsps |
| Windows | not available |
Represents the number of 1K blocks in swap area that is not allocated.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 24 Hours |
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | swap |
| HP | swapinfo |
| Linux | /proc/swaps |
| HP Tru64 | swapon |
| IBM AIX | lsps |
| Windows | not available |
Check the swap usage using the UNIX top command or the Solaris swap -l command. Additional swap can be added to an existing file system by creating a swap file and then adding the file to the system swap pool. (See documentation for your UNIX OS). If swap is mounted on /tmp, space can be freed by removing any junk files in /tmp. If it is not possible to add file system swap or free up enough space, additional swap will have to be added by adding a raw disk partition to the swap pool. See UNIX documentation for procedures.
Represents the size of the swap file.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 24 Hours |
The Switch/Swap Activity metric displays the metric reports on the system switching and swapping activity.
The data sources for this metric category include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | sar command |
| HP Tru64 | not available |
| IBM AIX | sar command |
| Windows | not available |
Represents the number of process context switches per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | not available |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.
Represents the number of 512-byte units transferred for swapins per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | sar command |
| HP Tru64 | not available |
| IBM AIX | not available |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.
Represents the number of 512-byte units transferred for swapouts per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | not available |
| IBM AIX | not available |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.
Represents the number of process swapins per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | sar command |
| HP Tru64 | not available |
| IBM AIX | not available |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.
Represents the number of process swapouts per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | sar command |
| HP Tru64 | not available |
| IBM AIX | not available |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. Also, the data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of processes swapped in over this five-second period divided by five.
The System Calls metric provides statistics about the system calls made over a five-second interval.
The data sources for this metric category include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
Represents the number of characters transferred by read system calls (block devices only) per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of system calls made over this period divided by the period.
Represents the number of characters transferred by write system calls (block devices only) per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of system calls made over this period divided by the period.
Represents the number of exec() system calls made per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of system calls made over this period divided by the period.
Represents the number of fork() system calls made per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of system calls made over this period divided by the period.
Represents the number of read() system calls made per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of system calls made over this period divided by the period.
Represents the number of system calls made per second. This includes system calls of all types.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of system calls made over this period divided by the period.
Represents the number of write() system calls made per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval. The results are essentially the number of system calls made over this period divided by the period.
The Top Processes metric is a listing of (up to) 20 processes that include 10 processes consuming the largest percentage of memory and 10 processes consuming the most percentage of CPU time. The processes are listed in the order of memory consumption.
Represents the command and all its arguments.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | ps command, for example, ps -efo args
|
| HP | ps command, for example, ps -efo args
|
| Linux | ps command, for example, ps -efo args
|
| HP Tru64 | ps command, for example, ps -efo args
|
| IBM AIX | ps command, for example, ps -efo args
|
| Windows | performance data counters |
Represents the CPU utilization time in seconds.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | ps command, for example, ps -efo time
|
| HP | ps command, for example, ps -efo time
|
| Linux | ps command, for example, ps -efo time
|
| HP Tru64 | ps command, for example, ps -efo time
|
| IBM AIX | ps command, for example, ps -efo time
|
| Windows | performance data counters |
Represents the percentage of CPU time consumed by the process.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | ps command, for example, ps -efo pcpu
|
| HP | ps command, for example, ps -efo pmem
|
| Linux | ps command, for example, ps -efo pcpu
|
| HP Tru64 | ps command, for example, ps -efo pcpu
|
| IBM AIX | ps command, for example, ps -efo pcpu
|
| Windows | performance data counters |
For UNIX-based platforms, check the load on the system using the UNIX uptime or top commands. Also, check for processes using too much CPU time by using the top and ps -ef commands. Note that the issue may be a large number of instances of one or more processes, rather than a few processes each taking up a large amount of CPU time. Kill processes using excessive CPU time.
Represents the percentage of memory consumed by the process.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | ps command, for example, ps -efo pmem
|
| HP | ps command, for example, ps -efo pmem
|
| Linux | ps command, for example, ps -efo pmem
|
| HP Tru64 | ps command, for example, ps -efo pmem
|
| IBM AIX | ps command, for example, ps -efo pmem
|
| Windows | performance data counters |
Represents the number of kilobytes of physical memory being used.
Represents the user name that owns the process, that is, the user ID of the process being reported on.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | ps command, for example, ps -efo user
|
| HP | ps command |
| Linux | ps command, for example, ps -efo user
|
| HP Tru64 | ps command, for example, ps -efo user
|
| IBM AIX | ps command, for example, ps -efo user
|
| Windows | Windows API |
Represents the total size of the process in virtual memory in kilobytes (KB).
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | ps command, for example, ps -efo vsz
|
| HP | ps command, for example, ps -efo vsz
|
| Linux | ps command, for example, ps -efo vsz
|
| HP Tru64 | ps command, for example, ps -efo vsz
|
| IBM AIX | ps command, for example, ps -efo vsz
|
| Windows | Windows API |
This metric reports tty device activity.
Represents the number of received incoming character interrupts per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.
Represents the input characters processed by canon() per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.
Represents the modem interrupt rate.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.
Represents the number of transmit outgoing character interrupts per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.
Represents the number of output characters per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.
Represents the raw input characters per second.
The data sources for this metric include the following:
| Host | Data Source |
|---|---|
| Solaris | sar command |
| HP | sar command |
| Linux | not available |
| HP Tru64 | table() system call |
| IBM AIX | sar command |
| Windows | not available |
The OS sar command is used to sample cumulative activity counters maintained by the OS. The data is obtained by sampling system counters once in a five-second interval.
The UDM metric allows you to execute your own scripts. The data returned by these scripts can be compared against thresholds and generate severity alerts similar to alerts in predefined metrics. UDM is similar to the Oracle9i Management Agent's UDE functionality.
The Users metric provides information about the users currently on the system being monitored.
Represents the number of times a user with a certain user name is logged on to the host target.