Oracle® Enterprise Manager Framework, Host, and Services Metric Reference Manual 12c Release 1 (12.1.0.2.0) Part Number E25162-03 |
|
|
PDF · Mobi · ePub |
The host metrics provide description, collection statistics, data source, multiple thresholds (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.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The cumulative number of blocks Read by the process over its lifetime. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The cumulative number of blocks Written by the process over its lifetime. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The cumulative number of Messages Received by the process over its lifetime. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The cumulative number of Messages Sent by the process over its lifetime. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The cumulative number of Signals taken by the process over its lifetime. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The number of processes owned by the project measured in the aggregate. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The percent CPU time used by the process. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The ratio of the process resident set size to physical memory. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The resident set size of the process in kilobytes. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The size of the process virtual address space in kilobytes. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The number of threads active in the current Process. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The cumulative number of blocks Read by the process over its lifetime. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The cumulative number of blocks Written by the process over its lifetime. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The cumulative number of Messages Received by the process over its lifetime. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The cumulative number of Messages Sent by the process over its lifetime. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The cumulative number of Signals taken by the process over its lifetime. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The number of processes owned by the user measured in the aggregate. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The number of threads active in the current Process. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The percent CPU time used by the process. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The ratio of the process resident set size to physical memory. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The resident set size of the process in kilobytes. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
The size of the process virtual address space in kilobytes. This metric is available only on Solaris version 9 and later.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
The Solaris CIM Object Manager
Specific to your site.
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.
Represents the number of reads from block devices to buffer cache as a percentage of all buffer read
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 2-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 5 Minutes |
After Every Sample |
> |
Not Defined |
Not Defined |
6 |
Buffer Cache Read Hit Ratio %value%%% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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 |
Specific to your site.
Represents the number of reads performed on the buffer cache per second.
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 | sar command |
HP | sar command |
Linux | not available |
HP Tru64 | not available |
IBM AIX | sar command |
Windows | not available |
Specific to your site.
Represents the number of writes from block devices to buffer cache as a percentage of all buffer writes.
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 2-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 5 Minutes |
After Every Sample |
> |
Not Defined |
Not Defined |
6 |
Buffer Cache Read Hit Ratio %value%%% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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 |
Specific to your site.
Represents the number of writes performed on the buffer cache per second.
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 | sar command |
HP | sar command |
Linux | not available |
HP Tru64 | not available |
IBM AIX | sar command |
Windows | not available |
Specific to your site.
Represents the number of reads per second from character devices using physical I/O mechanisms.
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 | sar command |
HP | sar command |
Linux | not available |
HP Tru64 | table() system call |
IBM AIX | sar command |
Windows | not available |
An unusually high value may indicate an abnormal situation, so it is important to set thresholds based on the average value observed over a period of time. An abnormally high value may cause performance issues. The user action varies from case to case, observe the running processes to track down any errant process. Placing highly active directories on different disks may help.
Represents the number of writes per second from character devices using physical I/O mechanisms.
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 | sar command |
HP | sar command |
Linux | not available |
HP Tru64 | table() system call |
IBM AIX | sar command |
Windows | not available |
An unusually high value may indicate an abnormal situation, so it is important to set thresholds based on the average value observed over a period of time. An abnormally high value may cause performance issues. The user action varies from case to case, observe the running processes to track down any errant process. Placing highly active directories on different disks may help.
Represents the number of physical reads per second from block devices to the system buffer cache.
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 | sar command |
HP | sar command |
Linux | not available |
HP Tru64 | table() system call |
IBM AIX | sar command |
Windows | not available |
An unusually high value may indicate an abnormal situation, so it is important to set thresholds based on the average value observed over a period of time. An abnormally high value may cause performance issues. The user action varies from case to case, observe the running processes to track down any errant process. Placing highly active directories on different disks may help.
Represents the number of physical writes per second from block devices to the system buffer cache.
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 | sar command |
HP | sar command |
Linux | not available |
HP Tru64 | table() system call |
IBM AIX | sar command |
Windows | not available |
An unusually high value may indicate an abnormal situation, so it is important to set thresholds based on the average value observed over a period of time. An abnormally high value may cause performance issues. The user action varies from case to case, observe the running processes to track down any errant process. Placing highly active directories on different disks may help.
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.
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 |
The data sources for this metric 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 |
An abnormally high value (determined on the basis of historical data) indicates an underutilized cpu. The user action varies from case to case.
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.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
For this metric you can set different warning and critical threshold values for each "CPU Number" object.
If warning or critical threshold values are currently set for any "CPU Number" 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 "CPU Number" 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 data sources for this metric are Performance Data counters.
This indicates the amount of time spent by the processor in handling interrupts. If an unusually high value is observed, there is a possibility of some hardware
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 |
The data sources for this metric 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 |
An abnormally high value (determined on the basis of historical data) indicates that the machine is doing a lot of work at the system (kernel) level. The user action varies from case to case.
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 |
The data sources for this metric 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 |
An abnormally high value (determined on the basis of historical data) indicates the cpu is doing a lot of work at the user (application) level. An examination of the top processes on the system may help identify problematic processes.
This figure represents the percentage utilization of a CPU
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 cpu_stat) |
HP | pstat_getprocessor() system call |
Linux | /proc/stat |
HP Tru64 | not available |
IBM AIX | oracle_kstat() system call |
Windows | performance data counters |
An abnormally high value (determined on the basis of historical data) indicates that the system is under heavy load. If the value is consistently high, consider reducing the load on the system.
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 data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | not available |
HP | pstat_getprocessor() system call |
Linux | not available |
HP Tru64 | not available |
IBM AIX | oracle_kstat() system call |
Windows | performance data counters |
A high value indicates that the cpu spends a lot of time waiting for disk i/o to complete. Examine the disk errors and disk activity metrics to see if there are any problems with disk performance. Consider keeping heavily accessed directories on separate disks.
The metric provides information on the processors of the host.
This is the size of the Cache memory measured in MB.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/proc/cpuinfo
None.
This is the clock frequency of the processor.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/proc/cpuinfo
None.
This tells whether hyper threading is enabled for this processor or not.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/proc/cpuinfo
None.
Implementation type of processor.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/proc/cpuinfo
None.
This is the count the number rows having the same information in other columns like vendor_name or num_cores. This is added to make at least one key in table.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/proc/cpuinfo
None.
This is Die used to manufacture the CPU. Solaris prtdiag has CPU mask field. This column stores that information.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/proc/cpuinfo
None.
This represents number of cores per physical CPU. For example. for dual core processors this count will be two and for quad core processor this count will be four.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/proc/cpuinfo
None.
This is the revision.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/proc/cpuinfo
None.
This effectively represents the number of logical processor per physical processors. For example, for one dual core processor with hyper thread enabled, this value will be four.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/proc/cpuinfo
None.
This is vendor who has manufactured the processors. For example Intel and AMD.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/proc/cpuinfo
None.
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.
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 2-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 |
> |
Not Defined |
Not Defined |
6 |
Average service time for disk %keyvalue% is %value% ms, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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.
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | kernel statistics (class kstat_io) |
HP | pstat_getdisk system call |
Linux | iostat command |
HP Tru64 | table() system call |
IBM AIX | oracle_kstat() system call |
Windows | performance data counters |
This number should be low. A high number can indicate a disk that is slow due to excessive load or hardware issues. See also the CPU in IO-Wait (%) metric.
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.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
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.
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | kernel statistics (class kstat_io) |
HP | pstat_getdisk system call |
Linux | not available |
HP Tru64 | table() system call |
IBM AIX | oracle_kstat() system call |
Windows | performance data counters |
A high figure indicates a slow disk. Use the OS iostat -xn command to check wait time and service time for local disks and NFS mounted file systems. See also the CPU in IO-Wait (%) metric.
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 |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | kernel statistics (class kstat_io) |
HP | pstat_getdisk system call |
Linux | not available |
HP Tru64 | table() system call |
IBM AIX | oracle_kstat() system call |
Windows | performance data counters |
Specific to your site.
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 |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | kernel statistics (class kstat_io) |
HP | pstat_getdisk system call |
Linux | not available |
HP Tru64 | table() system call |
IBM AIX | oracle_kstat() system call |
Windows | performance data counters |
Specific to your site.
Represents the time spent in Input/Output operations (ms).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
Linux: /proc/diskstats or /proc/partitions
Specific to your site.
Represents the number of disk reads from the last collection.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
Linux: /proc/diskstats or /proc/partitions
Specific to your site.
Represents the number of disk reads from the last collection.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
Linux: /proc/diskstats or /proc/partitions
Specific to your site.
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 |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | kernel statistics (class kstat_io) |
HP | not available |
Linux | iostat command |
HP Tru64 | table() system call |
IBM AIX | oracle_kstat() system call |
Windows | performance data counters |
Specific to your site.
Represents the number of blocks (512 bytes) read per second.
Note: On HPUNIX, this metric is named Disk Blocks Transferred (per second).
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 kstat_io) |
HP | pstat_getdisk system call |
Linux | iostat command |
HP Tru64 | table() system call |
IBM AIX | oracle_kstat() system call |
Windows | performance data counters |
Specific to your site.
This metric represents disk device busy percentage.
Note: On HPUNIX, this metric is named Device Busy (%).
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 2-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 Sample |
> |
80 |
95 |
6 |
Disk Device %keyValue% is %value%%% busy. |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | kernel statistics (class kstat_io) |
HP | pstat_getdisk system call |
Linux | iostat command |
HP Tru64 | table() system call |
IBM AIX | oracle_kstat() system call |
Windows | performance data counters |
Specific to your site.
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 |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | kernel statistics (class kstat_io) |
HP | not available |
Linux | iostat command |
HP Tru64 | table() system call |
IBM AIX | oracle_kstat() system call |
Windows | performance data counters |
Specific to your site.
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 data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | kernel statistics (class kstat_io) |
HP | not available |
Linux | iostat command |
HP Tru64 | table() system call |
IBM AIX | oracle_kstat() system call |
Windows | performance data counters |
Specific to your site.
The Disk Device Errors metric provides the number of errors on the disk device.
These metrics are available only on 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.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 72 Hours |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | iostat -e command |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
Specific to your site.
Represents the error count of soft errors encountered while accessing the disk. Soft errors are synonymous to warnings.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 72 Hours |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | iostat -e command |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
Specific to your site.
Represents the sum of all errors on the particular device
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 72 Hours |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | iostat -e command |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
Specific to your site.
Represents the error count of network errors encountered. This generally indicates a problem with the network layer
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 72 Hours |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | iostat -e command |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
Specific to your site.
The Fans metric monitors the status of various fans present in the system.
This metric is available only on Dell Poweredge Linux Systems.
Represents the status of the fan.
This metric is available only on Dell Poweredge Linux Systems.
The following table lists the possible values for this metric and their meaning.
Metric Value | Meaning (per SNMP MIB) |
---|---|
1 | Other (not one of the following) |
2 | Unknown |
3 | Normal |
4 | Warning |
5 | Critical |
6 | Non-Recoverable |
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 2-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 15 Minutes |
Not Uploaded |
>= |
4 |
5 |
1 |
Status of Fan at device %FanIndex% in chassis %ChassisIndex% is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each unique combination of "Chassis Index" and "Fan Index" objects.
If warning or critical threshold values are currently set for any unique combination of "Chassis Index" and "Fan Index" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Chassis Index" and "Fan Index" objects, use the Edit Thresholds page.
SNMP MIB object: coolingDeviceStatus (1.3.6.1.4.1.674.10892.1.700.12.1.5)
None.
Provides a description of the location of the fan. Example values are "CPU Fan", "PCI Fan", and "Memory Fan".
This metric is available only on Dell Poweredge Linux Systems.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: coolingDeviceLocationName (1.3.6.1.4.1.674.10892.1.700.12.1.8)
None.
The File Access System Calls metric provides information about the usage of file access system calls.
This metric is available on Solaris, HP, and IBM AIX.
Represents the number of file system blocks read per second performing direct lookup.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
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.
None.
Represents the number of system iget() calls made per second. iget is a file access system routine.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
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 following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
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.
None.
The File and Directory Monitoring metric monitors various attributes of specific files and directories. Setting of key value specific thresholds triggers the monitoring of files or directories referred to in the given key value. The operator must specify key value specific thresholds to monitor any file or directory.
Reports issues encountered in fetching the attributes of the file or directory. Errors encountered in monitoring the files and directories specified by the key value based thresholds are reported.
Note: This metric is not available on IBM AIX.
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 2-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 15 Minutes |
After Every Sample |
!= |
Not Defined |
0 |
1 |
%file_attribute_not_found% . |
For this metric you can set different warning and critical threshold values for each "File or Directory Name" object.
If warning or critical threshold values are currently set for any "File or Directory 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 "File or Directory Name" object, use the Edit Thresholds page.
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points |
HP | perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points |
Linux | perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
Looks for the attributes for file and directories like inode id, user id, and group id. If not found an alert is raised so that user can verify.
Fetches the octal value of file permissions on the different variations of UNIX operating systems including Linux. Setting a key value specific warning or critical threshold value against this metric would result in the monitoring of a critical file or directory. For example, to monitor the file permissions for file name /etc/passwd, you should set a threshold for /etc/passwd.
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 2-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 15 Minutes |
After Every Sample |
!= |
Not Defined |
Not Defined |
1 |
Current permissions for %file_name% are %file_permissions%, different from warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each "File or Directory Name" object.
If warning or critical threshold values are currently set for any "File or Directory 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 "File or Directory Name" object, use the Edit Thresholds page.
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points |
HP | perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points |
Linux | perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points |
HP Tru64 | not available |
IBM AIX | perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points |
Windows | not available |
An alert will be raised if the permissions for a file or directory have changed. User may want to verify the change.
Fetches the current size of the given file or directory in megabytes. Setting a key value specific warning or critical threshold value against this metric would result in monitoring of a critical file or directory. For example, to monitor the file permissions for directory /absolute_directory_path, you should set a threshold for /absolute_directory_path.
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 2-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 15 Minutes |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
Size of %file_name% is %file_size% MB, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each "File or Directory Name" object.
If warning or critical threshold values are currently set for any "File or Directory 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 "File or Directory Name" object, use the Edit Thresholds page.
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points |
HP | perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points |
Linux | perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points |
HP Tru64 | not available |
IBM AIX | perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points |
Windows | not available |
If a threshold is exceeded, you may need to take action to adjust the file size or the threshold level.
Provides the value for the rate at which the file�s size is changing. Setting a key value specific warning or critical threshold value against this metric would result in monitoring of the critical file or directory. For example, to monitor the file change rate for the file name /absolute_file_path, the operator should set a threshold for /absolute_file_path.
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 2-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 15 Minutes |
After Every Sample |
> |
Not Defined |
Not Defined |
1 |
%file_name% is growing at the rate of %file_sizechangerate% (KB/hour), crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each "File or Directory Name" object.
If warning or critical threshold values are currently set for any "File or Directory 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 "File or Directory Name" object, use the Edit Thresholds page.
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points |
HP | perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points |
Linux | perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points |
HP Tru64 | not available |
IBM AIX | perl stat command for files; df for directories that are file system mount points; du for directories that are not file system mount points |
Windows | not available |
Rate of change of file/directory. An abnormally high value (determined on the basis of historical data) indicates sudden increase in size. Users may want to take some action based on alert.
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 |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | /etc/mnttab file entries |
HP | bdf command |
Linux | df command |
HP Tru64 | df command |
IBM AIX | /etc/mnttab file entries |
Windows | not available |
None.
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 |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | vminfo system |
HP | bdf command |
Linux | df command |
HP Tru64 | df command |
IBM AIX | stavfs() system call |
Windows | Windows API |
None.
Represents the percentage of free space available 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 2-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 15 Minutes |
After Every 24 Samples |
< |
20 |
5 |
1 |
Filesystem %keyValue% has %value%%% available space, fallen below warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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.
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | stavfs() system call |
HP | bdf command |
Linux | df command |
HP Tru64 | df command |
IBM AIX | stavfs() system call |
Windows | Windows API |
Use the OS du -k command to check which directories are taking up the most space (du -k|sort -rn).
Represents the total space, expressed in megabytes, allocated in the file system.
This metric is available only on Windows.
The data source for this metric is GetDiskFreeSpaceEx.
A high value indicates that the filesystem has very little free space remaining.User might want to manage the free space.
The Kernel Memory metric provides information on kernel memory allocation (KMA) activities.
This metric is available only on Solaris. The data source is the sar
command. The data is obtained by sampling system counters once in a five-second interval.
This metric represents the Number of requests for large memory that failed, that is, requests that were not satisfied.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | sar command
The data is obtained by sampling system counters once in a five-second interval. |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
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.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | sar command
The data is obtained by sampling system counters once in a five-second interval. |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
This metric represents the number of requests for small memory that failed, that is, requests that were not satisfied.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | sar command
The data is obtained by sampling system counters once in a five-second interval. |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
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.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | sar command
The data is obtained by sampling system counters once in a five-second interval. |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
This metric represents the amount of memory allocated for oversized memory requests.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | sar command
The data is obtained by sampling system counters once in a five-second interval. |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
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.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | sar command
The data is obtained by sampling system counters once in a five-second interval. |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
This metric represents the amount of memory, in bytes, the kernel allocated to satisfy large memory requests.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | sar command
The data is obtained by sampling system counters once in a five-second interval. |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
This metric represents the amount of memory, in bytes, the kernel allocated to satisfy small memory requests.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | sar command
The data is obtained by sampling system counters once in a five-second interval. |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
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.
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 2-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 5 Minutes |
After Every Sample |
> |
40 |
80 |
6 |
CPU I/O Wait is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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 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 2-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 |
> |
not defined |
not defined |
6 |
CPU in Kernel Mode, %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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 |
An abnormally high value (determined on the basis of historical data) indicates that the machine is doing a lot of work at the system (kernel) level. The user action varies from case to case.
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 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 2-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 |
> |
not defined |
not defined |
6 |
CPU in User Mode, %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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 |
An abnormally high value (determined on the basis of historical data) indicates the cpu is doing a lot of work at the user (application) level. An examination of the top processes on the system may help identify problematic processes.
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 data sources for this metric are Performance Data counters.
None.
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 data sources for this metric are Performance Data counters.
A consistently high value indicates a number of CPU bound tasks. This information should be corelated with other metrics such as Page Transfer Rate. Tuning the system, accompanied with additional memory, should help.
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 2-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 |
> |
80 |
95 |
6 |
CPU Utilization is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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 |
An abnormally high value (determined on the basis of historical data) indicates that the system is under heavy load. If the value is consistently high, consider reducing the load on the system.
Represents logical free memory in a system (discounting memory used for filesystem buffers). Note that this memory can potentially be freed, and may not be available immediately.
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 2-15 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 |
Logical Free Memory, %value%%%, gone below warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
Linux: /proc/meminfo
AIX: libperfstat
A very low value (determined on the basis of historical data) indicates that the system is running out of RAM and this could be due to one or more of the following reasons. The first is that there is more than the planned number of processes running on the system. The second is that the processes are taking a lot more memory than expected. The third reason is that a specific process is leaking memory consistently.
Represents logical free memory in a system (discounting memory used for filesystem buffers). Note that this memory can potentially be freed, and may not be available immediately.
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 2-16 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 |
Logical Free Memory, %value%%%, gone below warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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 |
On Linux OS this value might always be close to 0%. Please refer Free logical memory (%) for actual free memory that is available for the users. User should not take any action based on the value of this metric
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 Seconds |
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 2-17 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, crossed warning (%warning_threshold% /sec) or critical (%critical_threshold% /sec) threshold. |
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 |
If this number is zero or close to zero, then you can be sure the system has sufficient memory. If scan rate is always high, then adding memory will definitely help.
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 2-18 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 |
Memory Utilization is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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 |
On Linux OS this value might always be close to 100%. Please refer to Free logical memory (%) for actual free memory that is available for the users. User should not take any action based on the value of this metric.
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 system wide 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 data sources for this metric are Windows Performance counters.
High transfer rates indicate a memory contention. Adding memory would help.
Represents the average number of processes in memory and subject to be run in the last interval. This metric checks the run queue.
This metric is not available 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 2-19 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 |
CPU Load (Run Queue Length averaged over 1 minute) is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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.
This metric is not available 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 2-20 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 (Run Queue Length averaged over 5 minutes) is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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.
This metric is not available 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 2-21 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 |
CPU Load (Run Queue Length averaged over 5 minutes) is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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 2-22 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%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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 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 2-23 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 |
Disk totIO %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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 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 2-24 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 |
Number of processes is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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 |
An abnormally high value (determined on the basis of historical data) indicates that the system is under heavy load. If the value is consistently high, consider reducing the load on the system by stopping the number of processes.
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.
Performance Data counters and Windows API GlobalMemoryStatusEx
An abnormally high value (determined on the basis of historical data) indicates that the system is doing a lot of swapping by moving data either to or from the disk. This typically will slow down the system because of the relatively slower access to the disk. The reason for this could be one or more of the following:
There are many processes running on the system competing for a limited RAM and this results in more swapping. User can try to reduce the load by stopping some process
A process occupying more memory than expected leading to a shortage of available memory
Typically these kinds of problems are solved by adding more RAM.
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 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 2-25 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 |
Number of users is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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 |
An abnormally high value (determined on the basis of historical data) indicates that the system is under heavy load. If the value is consistently high, consider reducing the load on the system by restricting or removing active users from the system.
Represents the size in kilobytes of the page file instance used.
This metric is available only on Windows.
Performance Data counters and Windows API GlobalMemoryStatusEx.
An abnormally high value (determined on the basis of historical data) indicates that the system is doing a lot of swapping by moving data either to or from the disk. This typically will slow down the system because of the relatively slower access to the disk. The reason for this could be one or more of the following:
There are many processes running on the system competing for a limited RAM and this results in more swapping. User can try to reduce the load by stopping some process
A process occupying more memory than expected leading to a shortage of available memory
Typically these kinds of problems are solved by adding more RAM.
The Log File Monitoring metric allows the operator to monitor one or more log files for the occurrence of one or more perl patterns in the content. In addition, the operator can specify a perl pattern to be ignored for the log file. Periodic scanning will be performed against new content added since the last scan, lines matching the ignore pattern will be ignored first, then lines matching specified match patterns will result in one record being uploaded to the repository for each pattern. The user can set a threshold against the number of lines matching the given pattern. File rotation will be handled within the given file.
Returns the actual content if the given file has been specifically registered for content uploading, else it will return the count of lines that matched the pattern specified.
The operator can list the names of files or directories to be never monitored in <EMDROOT>/sysman/config/lfm_efiles file. The operator can list the names of the files or directories whose contents can be uploaded into Oracle Management Repository in <EMDROOT>/sysman/config/lfm_ifiles file.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
Oracle provided perl program that scans files for the occurrence of user specified perl patterns.
None.
Returns the number of lines matching the pattern specified in the given file. Setting warning or critical thresholds against this column for a specific {log file name, match pattern in perl, ignore pattern in perl} triggers the monitoring of specified criteria against the given log file.
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 2-26 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 |
> |
0 |
Not Defined |
1* |
%log_file_message% Crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
* Once an alert is triggered for this metric, it must be manually cleared.
For this metric you can set different warning and critical threshold values for each unique combination of "Log File Name", "Match Pattern in Perl", "Ignore Pattern in Perl", and "Time Stamp" objects.
If warning or critical threshold values are currently set for any unique combination of "Log File Name", "Match Pattern in Perl", "Ignore Pattern in Perl", and "Time Stamp" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Log File Name", "Match Pattern in Perl", "Ignore Pattern in Perl", and "Time Stamp" objects, use the Edit Thresholds page.
Oracle supplied perl program monitors the log files for user specified criteria.
None.
The Memory Devices metric monitors the status of memory devices configured in the system.
Represents the bank location name of the memory device, when applicable.
This metric is available only on Dell Poweredge Linux Systems.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: memoryDeviceStatus (1.3.6.1.4.1.674.10892.1.1100.50.1.5)
None.
Represents the location name of the memory device, for example, "DIMM A".
This metric is available only on Dell Poweredge Linux Systems.
Metric Value | Meaning (per SNMP MIB) |
---|---|
1 | Other (not one of the following) |
2 | Unknown |
3 | Normal |
4 | Warning |
5 | Critical |
6 | Non-Recoverable |
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: memoryDeviceStatus (1.3.6.1.4.1.674.10892.1.1100.50.1.5)
None.
Represents the status of the memory device.
This metric is available only on Dell Poweredge Linux Systems.
The following table lists the possible values for this metric and their meaning.
Metric Value | Meaning (per SNMP MIB) |
---|---|
1 | Other (not one of the following) |
2 | Unknown |
3 | Normal |
4 | Warning |
5 | Critical |
6 | Non-Recoverable |
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 2-27 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 |
Not Uploaded |
>= |
4 |
5 |
1 |
Status of Memory at bank location %MemoryBankLocation% and location %MemoryLocation% is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each unique combination of "Chassis" and "Index" objects.
If warning or critical threshold values are currently set for any unique combination of "Chassis" and "Index" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Chassis" and "Index" objects, use the Edit Thresholds page.
SNMP MIB object: memoryDeviceStatus (1.3.6.1.4.1.674.10892.1.1100.50.1.5)
None.
Represents the size, in kilobytes, of the memory device.
This metric is available only on Dell Poweredge Linux Systems.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: memoryDeviceSize (1.3.6.1.4.1.674.10892.1.1100.50.1.14)
None.
Represents the type of the memory device.
This metric is available only on Dell Poweredge Linux Systems.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: memoryDeviceSize (1.3.6.1.4.1.674.10892.1.1100.50.1.14)
None.
The Message and Semaphore Activity metric provides information about the message and semaphore activity of the host system being monitored.
The following table lists the metrics and their descriptions.
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.
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | sar command |
HP | sar command |
Linux | not available |
HP Tru64 | ipcs command |
IBM AIX | sar command |
Windows | not available |
None.
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 data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | sar command |
HP | sar command |
Linux | not available |
HP Tru64 | ipcs command |
IBM AIX | sar command |
Windows | not available |
None.
The metric holds the information about the IO cards in the host, including pci cards and USBs.
This is the bus type of the IO card.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
lspci
None.
The clock frequency of the IO card.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
lspci
None.
This represents the name of the IO card.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
lspci
None.
This represents the IO card revision.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
lspci
None.
This represents the manufacturer name of IO card.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
lspci
None.
This metric relates to network interface cards, both unbonded and bonded interface cards. Slave interface cards have the same information as bonded cards.
Broadcast address of the local area network.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
ifconfig
None.
Default gateway configured for this host.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
ifconfig
None.
A description of the Network Interface Card.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
ifconfig
None.
Represents whether this Network Interface Card (NIC) is configured for dynamic or static ip addresses
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
ifconfig
None.
Network interface card's Flags
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
ifconfig
None.
This represents the aliases for the host corresponding to this Network Interface Card.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
arp
None.
IP address associated with this Network Interface Card. This is supposed to be an IPV4 address.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
ifconfig
None.
This is comma-separated list of IPV6 addresses.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
ifconfig
None.
Hardware address of the Network Interface Card.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
ifconfig
None.
This is subnet mask inet address.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
ifconfig
None.
Maximum packet size that to be sent it from this Network Interface Card. This is in bytes.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
ifconfig
None.
Network interface card name.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
ifconfig
None.
This metric relates to bonded network interface cards. Slave interface cards have the same information as bonded cards.
Name of the bond.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
Mode of the bonds. This can be balance-alb.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
Options/properties of the bond. This can be something like "miimon=100 max_bonds=4."
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
Primary slave of the bond. The Network Interface Card which is the primary slave of the bond.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
Comma separated list of secondary slaves.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
This metric contains the operating summary information. There will be one row per host.
This is the OS address length. This is either 32 bit or 64 bit.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
uname -a
None.
Base version of the OS
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
uname -a
None.
When host is member Database Machine, this columns will have a value of 1.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
uname -a
None.
Default Run level of the OS running on the host. Whenever the OS is booted, it will be booted to this run level.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
uname -a
None.
This is only applicable for Linux. Represents OS distributed version
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
uname -a
None.
This represents Maximum swap space available for the OS.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
uname -a
None.
Name of the OS
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/etc/enterprise-release for OEL
/etc/redhat-release for redhat
/etc/UnitedLinux-release
/etc/SuSE-release
None.
This is the platform id number
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
uname -a
None.
Latest update level of this OS
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
uname -a
None.
This represents the OS vendor name.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/etc/enterprise-release for OEL
/etc/redhat-release for redhat
/etc/UnitedLinux-release
None.
This metric stores the information about OS components, including Patches, Bundles, and Packages.
Description of the component
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
None.
Installation date of the component.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
None.
Name of the OS component.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
None.
Type of OS components. This can be Patch, Bundle, Package.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
None.
Version of the component.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
None.
This lists all file systems mounted in the host.
File System capacity in GB.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/etc/mtab
None.
Applicable NT only.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/etc/mtab
None.
Mount location of the file system.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/etc/mtab
None.
This metric contains details about the mount options. These could be similar to "rw,intr,largefiles,logging,xattr,onerror=panic."
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/etc/mtab
None.
This is the device path of host. This can be /dev/hd10opt, Local Disk (C:)
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/etc/mtab
None.
This is the file system type. Examples include nfs, ntfs, and jfs.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/etc/mtab
None.
This metric lists some of the OS properties, including OPEN_MAX, Semaphore values, and kernel.pid_max.
Name of configuration variable of the OS, for example OPEN_MAX.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/getconf, ulimit
This is the source of the property info. This can be similar to /sbin/sysctl
or /usr/bin/getconf
.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/getconf , ulimit
This is the value of the property.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/getconf , ulimit
This metric contains details of all the OS Registered Software.
Any vendor description for the software.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
Informational only.
ID of Software installed in the host. Only applicable for NT/Windows.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
Informational only.
Installation date of the software.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
Informational only.
The location where the software is installed.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
Informational only.
Installation or distribution source of the installed product. For example, the package name, bundling application, or distro.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
Informational only.
Name of installed software.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
Informational only.
Vendor who provided the software
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
Informational only.
Anything related to software
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
Informational only.
Any vendor description for the software.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
Informational only.
Represents the Solaris zone name in which the product is installed.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
Informational only.
Parent ID of the installed product. Applicable to the Sun Service Tag product taxonomy
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
Informational only.
Descriptive parent name of the installed product. Applicable to the Sun Service Tag product taxonomy
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
Informational only.
CPU/OS architecture the application is designed to run on e.g., Solaris SPARC (64bit)
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
/bin/rpm
Informational only.
This metric contains details of the operating system ULIMITS.
Limits the size of a "core" file left behind when a process encounters a segmentation fault or other unexpected fatal error.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
Maximum CPU time a process can use before it get terminated. CPU time is the amount of time the CPU actual spends executing processor instructions and is often much less than the total program "runs time".
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
Limits the amount of memory that a process can allocate on the heap, as with malloc, calloc, C++ "new," and most object creation in higher-level languages. Specified in kilobytes.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
Maximum size of the file a process can create. Number will be in 512 bytes (one block).
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
This number represents maximum number of files that can be opened at a time.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
Limits the amount of memory a process can allocate on the stack, as in the case of local variables in C, C++, and many other languages.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
Maximum memory that can be allocated to a process. This includes all types of memory, including the stack, the heap, and memory-mapped files Attempts to allocate memory in excess of this limit will fail with an out-of-memory error.
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
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.
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 15 Minutes |
The data sources for the metrics in this 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 |
Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.
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 2-28 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%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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.
The data sources for the metrics in this 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 |
Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.
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 15 Minutes |
The data sources for the metrics in this 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 |
Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.
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 15 Minutes |
The data sources for the metrics in this 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 |
Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.
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 15 Minutes |
The data sources for the metrics in this 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 | not available |
IBM AIX | perfstat system call |
Windows | not available |
Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.
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 15 Minutes |
The data sources for the metrics in this 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 | not available |
IBM AIX | perfstat system call |
Windows | not available |
Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.
Represents the number of total errors per second, encountered on the network interface. It is the rate of read and write errors encountered on the network interface.
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 2-29 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 Error Rate for %keyvalue% is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
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.
It is computed as the sum of Network Interface Input Errors (%) and Network Interface Output Errors (%).
Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.
Represents the total I/O rate on the network interface. It is measured as the sum of Network Interface Read (MB/s) and Network Interface Write (MB/s).
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 2-30 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 I/O Rate for %keyvalue% is %value%MB/Sec, crossed warning (%warning_threshold%MB/Sec) or critical (%critical_threshold%MB/Sec) threshold. |
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.
It is computed as the sum of Network Interface Read (MB/s) and Network Interface Write (MB/s).
Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.
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 |
The data sources for the metrics in this 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 |
Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.
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 data sources for the metrics in this 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 | not available |
IBM AIX | perfstat system call |
Windows | not available |
Use the OS netstat -i command to check the performance of the interface. Also, check the system messages file for messages relating to duplex setting by using the OS grep -i command and searching for the word 'duplex'.
The Paging Activity metric provides the amount of paging activity on the system.
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 |
The data sources for the metrics in this category 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 |
Informational only.
The 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.
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 the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | not available |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | Performance Data counters |
Informational only.
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.
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 the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | not available |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | Performance Data counters |
Informational only
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.
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 the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | not available |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | Performance Data counters |
Informational only.
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 |
The data sources for the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | kernel statistics (class misc cpu_stat) |
HP | pstat_getvminfo system call |
Linux | not available |
HP Tru64 | not available |
IBM AIX | oracle_kstat() system call |
Windows | not available |
Informational only.
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.
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 the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | not available |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | Performance Data Counters |
Informational only.
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 |
The data sources for the metrics in this category 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 | perfstat system call |
Windows | not available |
Informational only.
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 system wide 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 the metrics in this category 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 |
Informational only.
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 |
The data sources for the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | kernel statistics (class misc cpu_stat) |
HP | pstat_getvminfo system call |
Linux | not available |
HP Tru64 | vmstat command |
IBM AIX | oracle_kstat() system call |
Windows | performance data counters |
Informational only.
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 the metrics in this 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 |
Informational only.
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 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 2-31 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 |
Pages Paged-out (per second) %value%, has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
The data sources for the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | kernel statistics (class misc cpu_stat) |
HP | pstat_getvminfo() system call |
Linux | sar command |
HP Tru64 | vmstat command |
IBM AIX | oracle_kstat() system call |
Windows | performance data counters |
Informational only.
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 the metrics in this category 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 |
Informational only.
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 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 2-32 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 |
Pages Paged-In (per second) %value%, has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
The data sources for the metrics in this category 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 |
If this number is zero or closer to zero, then you can be sure the system has sufficient memory. If the number is always high, then adding memory will definitely help.
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.
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 the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | not available |
HP | not available |
Linux | not available |
HP Tru64 | not available |
IBM AIX | not available |
Windows | performance data counters |
Informational only.
The Peripheral Component Interconnect (PCI) Devices metric monitors the status of PCI devices.
Descriptive name of the Dell Peripheral Component Interconnect (PCI) Device
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: pCIDeviceDescriptionName (1.3.6.1.4.1.674.10892.1.1100.80.1.9)
None.
Name of the Dell Peripheral Component Interconnect (PCI) Device
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: pCIDeviceManufacturerName (1.3.6.1.4.1.674.10892.1.1100.80.1.8)
None.
Represents the status of the Dell Peripheral Component Interconnect (PCI) Device.
This metric is available only on Dell Poweredge Linux Systems.
The following table lists the possible values for this metric and their meaning.
Metric Value | Meaning (per SNMP MIB) |
---|---|
1 | Other (not one of the following) |
2 | Unknown |
3 | Normal |
4 | Warning |
5 | Critical |
6 | Non-Recoverable |
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 2-33 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 |
Not Uploaded |
>= |
4 |
5 |
1 |
Status of PCIDevice %PCIDeviceIndex% in chassis %ChassisIndex% is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each unique combination of "Chassis Index", "PCI Device Index", and "System Slot Index" objects.
If warning or critical threshold values are currently set for any unique combination of "Chassis Index", "PCI Device Index", and "System Slot Index" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Chassis Index", "PCI Device Index", and "System Slot Index" objects, use the Edit Thresholds page.
SNMP MIB object: pCIDeviceStatus (1.3.6.1.4.1.674.10892.1.1100.80.1.5)
None.
The Power Supplies metric monitors the status of various power supplies present in the host system.
This metric is available only on Dell Poweredge Linux Systems.
Represents the location name of the power supply
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: powerSupplyLocationName (1.3.6.1.4.1.674.10892.1.600.12.1.8)
None.
Represents the maximum sustained output wattage of the power supply, in tenths of watts.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: powerSupplyOutputWatts (1.3.6.1.4.1.674.10892.1.600.12.1.6)
None.
Represents the status of the power supply.
This metric is available only on Dell Poweredge Linux Systems.
The following table lists the possible values for this metric and their meaning.
Metric Value | Meaning (per SNMP MIB) |
---|---|
1 | Other (not one of the following) |
2 | Unknown |
3 | Normal |
4 | Warning |
5 | Critical |
6 | Non-Recoverable |
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 2-34 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 |
Not Uploaded |
>= |
4 |
5 |
1 |
Status of Power Supply %PSIndex% in chassis %ChassisIndex% is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each unique combination of "Chassis Index" and "Power Supply Index" objects.
If warning or critical threshold values are currently set for any unique combination of "Chassis Index" and "Power Supply Index" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Chassis Index" and "Power Supply Index" objects, use the Edit Thresholds page.
SNMP MIB object: powerSupplyStatus (1.3.6.1.4.1.674.10892.1.600.12.1.5)
None.
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.
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 |
None.
Represents the CPU utilization time in seconds.
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 |
None.
Represents the percentage of CPU time consumed by the process.
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 |
None.
Represents the percentage of memory consumed by the process.
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 |
None.
Represents the number of kilobytes of physical memory being used.
Host | Data Source |
---|---|
Solaris | kernel memory structure (class vminfo) |
HP | ps command |
Linux | ps command |
HP Tru64 | ps command |
IBM AIX | kernel memory structure (struct vminfo) |
Windows | Windows API |
None.
Represents the user name that owns the process, that is, the user ID of the process being reported on.
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 |
None.
Represents the total size of the process in virtual memory in kilobytes (KB).
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 |
None.
The Process, Inode, File Tables Stats metric provides information about the process, inode, and file tables status.
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 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 data sources for the metrics in this 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 |
None.
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 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 data sources for the metrics in this 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 |
None.
Represents the maximum size of the inode table.
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 data sources for the metrics in this 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 |
None.
Represents the maximum size of the process table.
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 data sources for the metrics in this 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 |
None.
Represents the maximum size of the system file table.
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 data sources for the metrics in this 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 |
None.
Represents the number of allocated disk quota entries.
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 the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | not available |
HP | not available |
Linux | sar command |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
Provides the number of queued RT signals.
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 the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | not available |
HP | not available |
Linux | sar command |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
Provides the number of allocated super block handlers.
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 the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | not available |
HP | not available |
Linux | sar command |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
Represents the current size of the system file table.
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 the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | not available |
HP | not available |
Linux | sar command |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
Represents the Percentage Of Allocated Disk Quota Entries against the maximum number of cached disk quota entries that can be allocated.
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 2-35 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 |
Allocated Disk Quota Entries %value%%% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
The data sources for the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | not available |
HP | not available |
Linux | sar command |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
Represents the Percentage Of Allocated Super Block Handlers against the maximum number of super block handlers that Linux can allocate.
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 2-36 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 |
Queued RT Signals %value%%% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
The data sources for the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | not available |
HP | not available |
Linux | sar command |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
Represents the percentage of queued RT signals.
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 2-37 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 |
Queued RT Signals %value%%% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
The data sources for the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | not available |
HP | not available |
Linux | sar command |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
Represents the percentage of used file handles against the maximum number of file handles that the Linux kernel can allocate.
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 2-38 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 |
Used File Handles %value%%%, has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
The data sources for the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | not available |
HP | not available |
Linux | sar command |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
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.
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 the metrics in this 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 |
None.
Represents the current size of the inode table.
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 the metrics in this 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 |
None.
Represents the current size of the process table.
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 the metrics in this 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 |
The Processors metric monitors the state of each CPU in the host.
This metric is available only on Dell Poweredge Linux Systems.
Represents the family of the Dell processor devices.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: processorDeviceFamily (1.3.6.1.4.1.674.10892.1.1100.30.1.10)
None.
Represents the name of the manufacturer of the Dell processor.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: processorDeviceManufacturerName (1.3.6.1.4.1.674.10892.1.1100.30.1.8)
None.
Represents the status of the Dell processor device.
This metric is available only on Dell Poweredge Linux Systems.
The following table lists the possible values for this metric and their meaning.
Metric Value | Meaning (per SNMP MIB) |
---|---|
1 | Other (not one of the following) |
2 | Unknown |
3 | Normal |
4 | Warning |
5 | Critical |
6 | Non-Recoverable |
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 2-39 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 |
Not Uploaded |
>= |
4 |
5 |
1 |
Status of Processor %ProcessorIndex% in chassis %ChassisIndex% is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each unique combination of "Chassis Index" and "Processor Index" objects.
If warning or critical threshold values are currently set for any unique combination of "Chassis Index" and "Processor Index" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Chassis Index" and "Processor Index" objects, use the Edit Thresholds page.
SNMP MIB object: processorDeviceStatus (1.3.6.1.4.1.674.10892.1.1100.30.1.5)
None.
Represents the current speed of the Dell processor device in MegaHertz (MHz). A value of zero indicates the speed is unknown.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: processorDeviceCurrentSpeed (1.3.6.1.4.1.674.10892.1.1100.30.1.12)
None.
The Program Resource Utilization metric provides flexible resource monitoring functionality. The operator must specify the criteria for the programs to be monitored by specifying key value specific thresholds. Values for the key value columns {program name, owner} define the unique criteria to be monitored for resource utilization in the system.
By default, no programs will be tracked by this metric. Key Values entered as part of a key value specific threshold setting define the criteria for monitoring and tracking.
This metric is only available on Solaris.
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 the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | ps command |
HP | ps command |
Linux | ps command |
HP Tru64 | ps command |
IBM AIX | ps command |
Windows | ps command |
None.
Represents the maximum CPU time accumulated by the most active process matching the {program name, owner} key value criteria.
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 2-40 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 |
3 |
%prog_max_cpu_time_pid% process running program %prog_name% has accumulated %prog_max_cpu_time% minutes of cpu time. This duration crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each unique combination of "Program Name" and "Owner" objects.
If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Program Name" and "Owner" objects, use the Edit Thresholds page.
The data sources for the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | ps command |
HP | ps command |
Linux | ps command |
HP Tru64 | ps command |
IBM AIX | ps command |
Windows | not available |
None.
Represents the maximum percentage of CPU utilized by a single process matching the {program name, owner} key value criteria since last scan.
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 2-41 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 |
3 |
Process %prog_max_cpu_util_pid% matched by the program name ''%prog_name%'' and owner ''%owner%'' is utilizing %prog_max_cpu_util%%% of the cpu. It has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each unique combination of "Program Name" and "Owner" objects.
If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Program Name" and "Owner" objects, use the Edit Thresholds page.
The data sources for the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | ps command |
HP | ps command |
Linux | ps command |
HP Tru64 | ps command |
IBM AIX | ps command |
Windows | not available |
None.
Fetches the current number of processes matching the {program name, owner} key value criteria. It can be used for setting warning or critical thresholds to monitor for maximum number of processes that a given {program name, owner} key value criteria crosses.
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 2-42 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 |
3 |
%prog_max_process_count% processes are matched by the program name ''%prog_name%'' and owner ''%owner%''. They have crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each unique combination of "Program Name" and "Owner" objects.
If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Program Name" and "Owner" objects, use the Edit Thresholds page.
The data sources for the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | ps command |
HP | ps command |
Linux | ps command |
HP Tru64 | ps command |
IBM AIX | ps command |
Windows | not available |
None.
Represents the maximum resident memory occupied by a single process matching the {program name, owner} key value criteria. It can be used for setting warning or critical thresholds to monitor for maximum value a given {program name, owner} key value criteria crosses.
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 2-43 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 |
3 |
Process %prog_max_rss_pid% matched by the program name ''%prog_name%'' and owner ''%owner%'' is utilizing %prog_max_rss% (MB) of resident memory. It has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each unique combination of "Program Name" and "Owner" objects.
If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Program Name" and "Owner" objects, use the Edit Thresholds page.
The data sources for the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | ps command |
HP | ps command |
Linux | ps command |
HP Tru64 | ps command |
IBM AIX | ps command |
Windows | not available |
None.
Fetches the current number of processes matching the {program name, owner} key value criteria. It can be used for setting warning or critical thresholds to monitor for minimum number of processes that a given {program name, owner} key value criteria should never go under.
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 2-44 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 |
3 |
%prog_min_process_count% processes are matched by the program name ''%prog_name%'' and owner ''%owner%''. They have fallen below warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each unique combination of "Program Name" and "Owner" objects.
If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Program Name" and "Owner" objects, use the Edit Thresholds page.
The data sources for the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | ps command |
HP | ps command |
Linux | ps command |
HP Tru64 | ps command |
IBM AIX | ps command |
Windows | not available |
None.
Represents the total CPU time accumulated by all active process matching the {program name, owner} key value criteria.
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 2-45 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 |
3 |
%prog_max_process_count% processes matched by the program name ''%prog_name%'' and owner ''%owner%'' have accumulated %prog_total_cpu_time% minutes of cpu time. This duration has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each unique combination of "Program Name" and "Owner" objects.
If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Program Name" and "Owner" objects, use the Edit Thresholds page.
The data sources for the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | ps command |
HP | ps command |
Linux | ps command |
HP Tru64 | ps command |
IBM AIX | ps command |
Windows | not available |
None.
Represents the percentage of CPU time utilized by all active process matching the {program name, owner} key value criteria since last collection.
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 2-46 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 |
3 |
%prog_max_process_count% processes matched by the program name ''%prog_name%'' and owner ''%owner%'' are utilizing %prog_total_cpu_util%%% of the cpu. It has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each unique combination of "Program Name" and "Owner" objects.
If warning or critical threshold values are currently set for any unique combination of "Program Name" and "Owner" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Program Name" and "Owner" objects, use the Edit Thresholds page.
The data sources for the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | ps command |
HP | ps command |
Linux | ps command |
HP Tru64 | ps command |
IBM AIX | ps command |
Windows | not available |
None.
The Remote Access Card metric monitors the status of the Remote Access Card.
This metric is available only on Dell Poweredge Linux Systems.
Determines whether the dynamic host configuration protocol (DHCP) was used to obtain the network interface card (NIC) information.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: remoteAccessNICCurrentInfoFromDHCP (1.3.6.1.4.1.674.10892.1.1700.10.1.33)
None.
Represents the IP address for the gateway currently being used by the onboard network interface card (NIC) provided by the remote access (RAC) hardware.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: remoteAccessNICCurrentGatewayAddress (1.3.6.1.4.1.674.10892.1.1700.10.1.32)
None.
Provides the internet protocol (IP) address currently being used by the onboard network interface card (NIC) provided by the remote access (RAC) hardware.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: remoteAccessNICCurrentIPAddress (1.3.6.1.4.1.674.10892.1.1700.10.1.30)
None.
Represents the local area network (LAN) settings of the remote access hardware.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: remoteAccessLANSettings (1.3.6.1.4.1.674.10892.1.1700.10.1.15)
None.
Represents the subnet mask currently being used by the onboard network interface card (NIC) provided by the remote access (RAC) hardware.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: remoteAccessLANSettings (1.3.6.1.4.1.674.10892.1.1700.10.1.15)
None.
Represents the name of the product providing the remote access (RAC) functionality.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: remoteAccessProductInfoName (1.3.6.1.4.1.674.10892.1.1700.10.1.7)
None.
Represents the state of the remote access (RAC) hardware.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: remoteAccessStateSettings (1.3.6.1.4.1.674.10892.1.1700.10.1.5)
None.
Represents the status of the remote access (RAC) hardware.
This metric is available only on Dell Poweredge Linux Systems.
The following table lists the possible values for this metric and their meaning.
Metric Value | Meaning (per SNMP MIB) |
---|---|
1 | Other (not one of the following) |
2 | Unknown |
3 | Normal |
4 | Warning |
5 | Critical |
6 | Non-Recoverable |
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 2-47 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 |
Not Uploaded |
>= |
4 |
5 |
1 |
Status of Remote Access Card is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
SNMP MIB object: remoteAccessStatus (1.3.6.1.4.1.674.10892.1.1700.10.1.6)
None.
Represents the version of the product providing the remote access (RAC) functionality.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: remoteAccessVersionInfoName (1.3.6.1.4.1.674.10892.1.1700.10.1.9)
None.
The Storage Summary metrics collectively represent the summary of storage data on a host target. These metrics are derived from the various metrics collected and uploaded into the Oracle Management Repository by the Management Agent. They are computed every time the Management Agent populates the Management Repository with storage data. This collection is also triggered automatically whenever the user manually refreshes the host storage data from the Storage Details page.
Represents the total storage allocated to Oracle databases from Automatic Storage Management (ASM) instances on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the number of metric collection errors attributed to the storage related metrics of the Automatic Storage Management (ASM) targets on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the storage overhead of Automatic Storage Management (ASM) targets on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the storage available in Automatic Storage Management (ASM) targets on the host for allocating to databases.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the total free storage available in the databases on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the metric collection errors of storage related metrics of databases on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the total free storage available in the databases on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the storage allocated from the total disk storage available on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the storage that is available for allocation in disks on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the total number of storage related metric collection errors of the host target.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
The possible values for this metric are:
1 (one) if this host storage was computed successfully (sometimes with partial errors)
0 (zero) if the storage computation did not proceed at all due to some reasons (for example, failure to collect critical storage metric data).
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
The total free storage in all distinct local file systems on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
The total used space in all distinct local file systems on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the total number of Automatic Storage Management (ASM) instances, the storage data of which was used in computing storage summary of this host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the total number of databases, the storage data of which was used in computing storage summary of this host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the storage metric mapping issues on the host excluding the unmonitored server mapping errors.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the total number of Automatic Storage Management (ASM) instances on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the total number of databases on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the total storage allocated from the host-visible storage available on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the free storage available from the total allocated storage on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the overhead associated with storage on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the total unallocated storage on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the total storage used in the file systems and databases on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the total number of storage mapping issues that result from unmonitored Network File Systems (NFS) servers.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the total storage allocated from the volumes available on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the storage overhead in the volumes on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the storage available for allocation in the volumes on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the total free space available in all distinct writeable NFS mounts on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
Represents the storage used in all writeable NFS mounts on the host.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 24 hours or when the user manually refreshes storage data from the Storage Details page. |
These metrics are available on the Linux and Solaris hosts.
For more details on how these metrics are computed see the "About Storage Computation Formulas" topic in the Enterprise Manager online help. The online help also provides information about ASM, databases, disks, file systems, volumes, and storage details.
This metric is used to decide if the OS being monitored is supported or not. Its also used to inform the user if the number of Storage entities (Disks / FileSystems /Volumes) being monitored is within the applicable limits so as not to affect the performance of the Management Agent.
The metric is used to enable/disable the collection, depending on the OS supported or the number of storage entities being monitored.
The operating systems supported are Linux, Solaris, AIX, and HPUX.
The maximum number of storage entities monitored is set to 100 in the configuration file located in EMAgent/sysman/emd/emagent_storage.config. The Disks/Files/Volumes to be monitored can be added in the configuration file. If the storage entities are more than 100, the response time of the Management Agent increases.
Not available
Edit the configuration file (emagent/sysman/emd/emagent_storage.config), and add the Disks, Filesystems, and Volumes to be monitored.
The Swap Area Status metric provides the status of the swap memory on the system.
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 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 2-48 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 24 hours |
After Every Sample |
< |
Not Defined |
Not Defined |
1 |
Swap Free Size %value% has gone below the warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each "Swap File" object.If warning or critical threshold values are currently set for any "Swap File" 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 "Swap File" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
The data sources for the metrics in this category 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 data sources for the metrics in this category include the following:
Host | Data Source |
---|---|
Solaris | swap |
HP | swapinfo |
Linux | /proc/swaps |
HP Tru64 | swapon |
IBM AIX | lsps |
Windows | not available |
None.
The Switch/Swap Activity metric displays the metric reports on the system switching and swapping activity.
Number of process context switches per second
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 2-49 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 |
Process Context Switches (per second) %value% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
The data sources for the metrics in this category 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.
None.
Represents the number of 512-byte units transferred for swapins per second.
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 2-50 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 |
Swapins Transfers (per second) %value% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
The data sources for the metrics in this 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 |
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.
None.
Represents the number of 512-byte units transferred for swapouts per second.
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 2-51 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 |
Swapins Transfers (per second) %value% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
The data sources for the metrics in this 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 |
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.
None.
Represents the number of process swapins per second.
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 2-52 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 |
System Swapins (per second) %value% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
The data sources for the metrics in this 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 |
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.
None.
Represents the number of process swapouts per second.
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 2-53 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 |
System Swapouts (per second) %value% , has crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
The data sources for the metrics in this 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 |
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.
None.
The System BIOS (Basic Input/Output System) metric monitors the BIOS status for Dell Poweredge Linux systems.
Represents the manufacturer's name of the System BIOS (Basic Input/Output System). This metric is available only on Dell Poweredge Linux Systems.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: systemBIOSManufacturerName (1.3.6.1.4.1.674.10892.1.300.50.1.11)
None.
Represents the image size of the System BIOS (Basic Input/Output System) in kilobytes. A value of zero indicates that the size is unknown. This metric is available only on Dell Poweredge Linux Systems.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: systemBIOSSize (1.3.6.1.4.1.674.10892.1.300.50.1.6)
None.
Represents the status of the System BIOS (Basic Input/Output System) in this chassis.
This metric is available only on Dell Poweredge Linux Systems.
The following table lists the possible values for this metric and their meaning.
Metric Value | Meaning (per SNMP MIB) |
---|---|
1 | Other (not one of the following) |
2 | Unknown |
3 | Normal |
4 | Warning |
5 | Critical |
6 | Non-Recoverable |
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 2-54 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 |
Not Uploaded |
>= |
4 |
5 |
1 |
Status of BIOS %BiosIndex% in chassis %ChassisIndex% is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each unique combination of "Chassis Index" and "System BIOS Index" objects.
If warning or critical threshold values are currently set for any unique combination of "Chassis Index" and "System BIOS Index" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Chassis Index" and "System BIOS Index" objects, use the Edit Thresholds page.
SNMP MIB object: systemBIOSStatus (1.3.6.1.4.1.674.10892.1.300.50.1.5)
None.
Represents the version name of the System BIOS (Basic Input/Output System). This metric is available only on Dell Poweredge Linux Systems.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: systemBIOSVersionName (1.3.6.1.4.1.674.10892.1.300.50.1.8)
None.
The System Calls metric provides statistics about the system calls made over a five-second interval.
Represents the number of characters transferred by read system calls (block devices only) per second.
The data sources for the metrics in this 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 |
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.
None.
Represents the number of characters transferred by write system calls (block devices only) per second.
The data sources for the metrics in this 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 |
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.
None.
Represents the number of exec() system calls made per second.
The data sources for the metrics in this 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 |
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.
None.
Represents the number of fork() system calls made per second.
The data sources for the metrics in this 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 |
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.
None.
Represents the number of read() system calls made per second.
The data sources for the metrics in this 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 |
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.
None.
Represents the number of system calls made per second. This includes system calls of all types.
The data sources for the metrics in this 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 |
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.
None.
Represents the number of write() system calls made per second.
The data sources for the metrics in this 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 |
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.
None.
The Temperature metric monitors the hotness or coldness of the temperature probe.
This metric is available only on Dell Poweredge Linux Systems.
Represents the current reading of the temperature probe. The value is representing temperature in tenths of degrees Centigrade.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: temperatureProbeReading (1.3.6.1.4.1.674.10892.1.700.20.1.6)
An abnormally high value indicates that the system is doing a lot of work and getting overheated. The system could be overheated due to inadequate cooling by the Fan.
Provides a description of the location name of the temperature probe. Examples of values are: "CPU Temp" and "System Temp".
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: temperatureProbeLocationName (1.3.6.1.4.1.674.10892.1.700.20.1.8)
None.
Represents the status of the temperature probe.
This metric is available only on Dell Poweredge Linux Systems.
The following table lists the possible values for this metric and their meaning.
Metric Value | Meaning (per SNMP MIB) |
---|---|
1 | Other (not one of the following) |
2 | Unknown |
3 | Normal |
4 | Warning |
5 | Critical |
6 | Non-Recoverable |
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 2-55 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 |
Not Uploaded |
>= |
4 |
5 |
1 |
Temperature at probe %ProbeIndex% in chassis %ChassisIndex% is %TemperatureReading% (C). Status is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each unique combination of "Chassis Index" and "Temperature Probe Index" objects.
If warning or critical threshold values are currently set for any unique combination of "Chassis Index" and "Temperature Probe Index" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Chassis Index" and "Temperature Probe Index" objects, use the Edit Thresholds page.
SNMP MIB object: temperatureProbeStatus (1.3.6.1.4.1.674.10892.1.700.20.1.5)
This describes the status of the temperature probe. A failed probe needs to be physically examined or replaced.
This metric reports tty device activity.
Represents the number of received incoming character interrupts per second.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
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.
None.
Represents the input characters processed by canon() per second.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
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.
None.
Represents the modem interrupt rate.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
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.
None.
Represents the number of transmit outgoing character interrupts per second.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
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.
None.
Represents the number of output characters per second.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
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.
None.
Represents the raw input characters per second.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Seconds |
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.
None.
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.
The purpose of this metric is to collect those entries from all available Windows NT event log files whose type is either Error or Warning. A critical or a warning alert is raised only for System and Security Event log file entries.
Note: Since log files continue to grow, this metric outputs log events which had been written to the log file after the last collection time, that is, only those records are written out whose timeGenerated (time when the event was generated) is after the last collection time until the last record of the log file. If this metric is collected for the first time, only the events generated on the current date are outputted.
This metric is available only on Windows.
List of all categories for the events matching Log Name, Source, and Event ID defined for the monitored object. The actual category of the event can be found in the Windows event log message.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 15 Minutes |
Windows Management Instrumentation (WMI)
None.
This is the time at which point the metric scanned through the event logs. This metric is available only on Windows.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 15 Minutes |
Windows Management Instrumentation (WMI)
None.
This metric is a digest of all the events that match the Log Name, Source, and Event ID specified for the monitored object. After the above filtering is done, grouping of these events is done on Log Name, Source, Event ID, Category, and User to get the count of error events and warning events. The column has the details of the events in the following format:
[LogName: Source:Event ID:Category:User : :]
Example: [Application:Symantec AntiVirus:2: : :error=2:] [Application:Symantec AntiVirus:3: : ::warning =1 ]
To get the exact message about the events that satisfied the criteria set on the monitored object, the Event viewer provided by Microsoft Windows must be used.
This metric is available only on Windows.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 15 Minutes |
Windows Management Instrumentation (WMI)
None.
This is the Perl pattern to match the string defined for the Event ID in the monitored objects. The actual Event ID of the event can be found in the Windows event log message. This metric is available only on Windows.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
3.0 and higher | Every 15 Minutes |
Windows Management Instrumentation (WMI)
None.
The seriousness of the event. Possible values are: Warning and Error.
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 2-56 Metric Summary Table
Target Version | Key | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|---|
All Versions |
logfile: "system" |
Every 15 Minutes |
After Every Sample |
= |
warning |
error |
1* |
X1User[%user%]:Category[%categorystring%]:Description[%message%] |
* Once an alert is triggered for this metric, it must be manually cleared.
For this metric you can set different warning and critical threshold values for each unique combination of "Log Name", "Source", and "Event ID" objects.
If warning or critical threshold values are currently set for any unique combination of "Log Name", "Source", and "Event ID" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Log Name", "Source", and "Event ID" objects, use the Edit Thresholds page.
WMI Operating System Classes
None.
The Zombie Processes metric monitors the orphaned processes in the different variations of UNIX systems.
Represents the percentage of all processes running on the system that are currently in zombie state.
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 | ps command |
HP | ps command |
Linux | ps command |
HP Tru64 | ps command |
IBM AIX | ps command |
Windows | ps command |
None.
Represents the percentage of all processes running on the system that are currently in zombie state.
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 2-57 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 60 Samples |
> |
35 |
50 |
1 |
%value%%% of all processes are in zombie state, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
The data sources for this metric include the following:
Host | Data Source |
---|---|
Solaris | ps command |
HP | ps command |
Linux | ps command |
HP Tru64 | not available |
IBM AIX | not available |
Windows | not available |
None.
These metrics provide details on the throughput performance of each link (port-to-port connection) in the network, an aggregation of performance for Switch-to-Node and Switch-to-Switch link types, and total throughput performance of the network.
This is the throughput performance of each link (switch port to node/switch port connection) in the network
This is the globally unique identifier of the switch in this link (the first switch, if both end points are switches).
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, perfquery
No user action is required.
This is the port number of the switch in this link (the first switch, if both end points are switches).
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, perfquery
No user action is required.
This is either Switch-to-Switch or Switch-to-Node
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, perfquery
No user action is required.
This is the number of GB sent and received over this link in the last collection interval, divided by the duration of the last collection interval (Gbps).
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, perfquery
No user action is required.
These metrics describe the performance of each port of the switch and the aggregation of performance for Switch-to-Node and Switch-to-Switch link types. They also define whether a switch is a subnet manager for the network or not. Switch statistics are also covered.
Performance of each port of the switch
This is the port number of this switch in this link
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This is the globally unique identifier to which this port is connected
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This is the type of the entity to which this port is connected (for example, compute node, cell or switch)
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
f the port is connected to a switch, the GUID in "Connected to GUID" column is the switch GUID, else if the port is connected to a node, the GUID is the port GUID of the port on the node.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This is the port number of the entity to which this switch port is connected.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This is the supported speed of this link (Gbps).
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This is the supported width of this link (for example, 1X or 4X)
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This is the enabled speed of this link (Gbps).
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This is the enabled width of this link (for example, 1X or 4X)
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This is the active speed of this link (Gbps)
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This is the active width of this link (for example, 1X or 4X)
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This is the ink speed or width is less than the enabled speed or width respectively, the link is operating in degraded mode
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
By default, warning alert is issued if the link becomes degraded. User needs to evaluate the impact of this link on the performance of the database machine, and take appropriate steps to restore the link to normal speed/width.
This shows whether the link is up or down.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This shows whether the physical link is up or down.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This shows the number of GB sent and received over this link in the last collection interval, divided by the duration of the last collection interval (Gbps)
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This shows the number of errors of this type in the last collection interval.
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This shows the number of errors of this type in the last collection interval
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This shows the number of errors of this type in the last collection interval
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This shows the number of errors of this type in the last collection interval
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This shows the number of errors of this type in the last collection interval
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This shows the number of errors of this type in the last collection interval
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This shows the number of errors of this type in the last collection interval
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This shows the number of errors of this type in the last collection interval
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This shows the number of errors of this type in the last collection interval
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This shows the number of errors of this type in the last collection interval
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This shows the number of errors of this type in the last collection interval
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This shows the number of errors of this type in the last collection interval
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
No user action is required.
This is the total number of errors in the last collection interval
Metric Summary for Database Control
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
iblinkinfo.pl, ibportstate, perfquery
Set some threshold above which the number of errors is deemed high enough to merit scrutiny of potential impact on throughput performance