This metric category provides data on aggregate resource usage on a per project basis. This metric category is available only for Solaris version 9 and later.
This metric displays the cumulative number of seconds that this process has spent waiting for CPU over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent sleeping in Data Page Faults over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of Major Page Faults engendered by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of Minor Page Faults engendered by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of character I/O bytes Read and Written by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of blocks Read by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of blocks written by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of Involuntary Context Switches made by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of Messages Received by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of Messages Sent by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of Signals taken by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of system calls made by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of Voluntary Context Switches made by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent sleeping on User Lock Waits over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent sleeping in all other ways over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent Stopped over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of swap operations engendered by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent in System mode over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent sleeping in System Page Faults over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent in System Traps over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent sleeping in Text Page Faults over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent in User mode over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the number of processes owned by the project measured in the aggregate.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the percentage of CPU time used by the process.
| Target Version | Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
|---|---|---|---|---|
|
Solaris version 9 and later |
Every 15 Minutes |
Not Defined |
Not Defined |
User CPU Time is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the project name.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the ratio of the process resident set size to physical memory.
| Target Version | Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
|---|---|---|---|---|
|
Solaris version 9 and later |
Every 15 Minutes |
Not Defined |
Not Defined |
User Process Memory Size is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the total number of KiloBytes of memory consumed by the process heap at the time that it is sampled.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the resident set size of the process in kilobytes.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the size of the process virtual address space in kilobytes.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric category provides data on aggregate resource usage on a per user basis.
This metric category is available for Solaris version 9 and later only.
This metric displays the cumulative number of seconds that this process has spent waiting for CPU over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent sleeping in data page faults over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of major page faults engendered by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of minor page faults engendered by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of character I/O bytes read and written by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of blocks read by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of blocks written by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of involuntary context switches made by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of messages received by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of messages sent by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of signals taken by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of system calls made by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of voluntary context switches made by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent stopped over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent in system mode over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent sleeping in system page faults over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent in system traps over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of swap operations engendered by the process over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent sleeping in text page faults over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent sleeping on user lock waits over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent in user mode over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the cumulative number of seconds that this process has spent sleeping in all other ways over its lifetime.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the number of processes owned by the user measured in the aggregate.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the number of threads active in the current process.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the percent CPU time used by the process.
| Target Version | Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
|---|---|---|---|---|
|
Solaris version 9 and later |
Every 15 Minutes |
Not Defined |
Not Defined |
User CPU Time is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the ID associated with the user.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the ratio of the process resident set size to physical memory.
| Target Version | Collection Frequency | Default Warning Threshold | Default Critical Threshold | Alert Text |
|---|---|---|---|---|
|
Solaris version 9 and later |
Every 15 Minutes |
Not Defined |
Not Defined |
User Process Memory Size is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the total number of kilobytes of memory consumed by the process heap at the time that it is sampled.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
This metric displays the resident set size of the process in kilobytes.
|
Data Source
The Solaris CIM Object Manager
User Action
Specific to your site.
The metrics in this category provide information about the status of the boot environment.
This metric specifies if the boot environment will start up on the next reboot of the system.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the name of the boot environment.
|
Data Source
The data source for this metric includes the following:
|
This metric specifies if the boot environment is active now.
|
Data Source
The data source for this metric includes the following:
|
This metric specifies if the boot environment is bootable.
|
Data Source
The data source for this metric includes the following:
|
The Buffer Activity metric category 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.
This metric represents the number of reads from block devices to buffer cache as a percentage of all buffer reads.
|
Data Source
The data sources for this metric include the following:
|
User Action
Specific to your site.
This metric represents the number of reads performed on the buffer cache per second.
|
Data Source
The data sources for this metric include the following:
|
User Action
Specific to your site.
This metric represents the number of writes from block devices to buffer cache as a percentage of all buffer writes.
|
Data Source
The data sources for this metric include the following:
|
User Action
Specific to your site.
This metric represents the number of writes performed on the buffer cache per second.
|
Data Source
The data sources for this metric include the following:
|
User Action
Specific to your site.
This metric represents the number of reads per second from character devices using physical I/O mechanisms.
|
Table 2-1 Metric Summary Table
|
Data Source
The data sources for this metric include the following:
|
User Action
An unusually high value might 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.
This metric represents the number of writes per second from character devices using physical I/O mechanisms.
|
Table 2-2 Metric Summary Table
|
Data Source
The data sources for this metric include the following:
|
User Action
An unusually high value might 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.
This metric represents the number of physical reads per second from block devices to the system buffer cache.
|
Table 2-3 Metric Summary Table
|
Data Source
The data sources for this metric include the following:
|
User Action
An unusually high value might 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.
This metric represents the number of physical writes per second from block devices to the system buffer cache.
|
Table 2-4 Metric Summary Table
|
Data Source
The data sources for this metric include the following:
|
User Action
An unusually high value might 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 metrics in this category provide information about the temperature of the compute node.
This metric displays the name of the compute node.
|
The CPUs Details configuration metrics provide information about the processors of the host. Configuration metrics are not available from the All Metrics page of the Cloud Control console.
To view the CPUs Details configuration metrics:
From the Cloud Control UI, select your Host target type.
Right-click the target type name, and select Configuration, then select Last Collected.
The metrics appear under Latest Configuration.
This is the size of the Cache memory measured in MB.
|
Data Source
/proc/cpuinfo
User Action
None.
This is the clock frequency of the processor.
|
Data Source
/proc/cpuinfo
User Action
None.
This tells whether hyper threading is enabled for this processor.
|
Data Source
/proc/cpuinfo
User Action
None.
Implementation type of processor.
|
Data Source
/proc/cpuinfo
User Action
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.
|
Data Source
/proc/cpuinfo
User Action
None.
This is used to manufacture the CPU. Solaris prtdiag has CPU mask field. This column stores that information.
|
Data Source
/proc/cpuinfo
User Action
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.
|
Data Source
/proc/cpuinfo
User Action
None.
This is the revision.
|
Data Source
/proc/cpuinfo
User Action
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.
|
Data Source
/proc/cpuinfo
User Action
None.
The metrics in this category provide information about the CPU frequency state.
This metric provides the CPU clock frequency in Mhz.
|
Data Source
The data source for this metric includes the following:
|
The metrics in this category provide information about the CPU power state.
This metric displays the CPU power state.
|
Data Source
The data source for this metric includes the following:
|
This metric displays the average time in milliseconds spent in the CPU power state.
|
Data Source
The data source for this metric includes the following:
|
The metric in this category provides information about the overall average CPU usage.
This metric provides the percentage of the overall CPU usage.
|
Data Source
The data sources for this metric include the following:
|
The CPU Usage metric category 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.
This metric 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).
|
Data Source
The data sources for this metric include the following:
|
User Action
An abnormally high value (determined on the basis of historical data) indicates an underutilized cpu. The user action varies from case to case.
This metric 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.
|
Multiple Thresholds
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.
Data Source
The data sources for this metric are Performance Data counters.
User Action
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
This metric provides the user-specified CPU number .
|
This metric 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).
|
Data Source
The data sources for this metric include the following:
|
User Action
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.
This metric 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).
|
Data Source
The data sources for this metric include the following:
|
User Action
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
|
Data Source
The data sources for this metric include the following:
|
User Action
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.
This metric 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).
|
Data Source
The data sources for this metric include the following:
|
User Action
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 Disk Activity metric category 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.
This metric represents the sum of average wait time and average run time.
|
This metric represents the average time spent by the command waiting on the queue for getting executed.
|
Multiple Thresholds
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.
Data Source
The data sources for this metric include the following:
|
User Action
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.
This metric represents the average number of commands waiting for service (queue length).
|
Data Source
The data sources for this metric include the following:
|
User Action
Specific to your site.
This metric represents the average time spent by the command on the active queue waiting for its execution to be completed.
|
Data Source
The data sources for this metric include the following:
|
User Action
Specific to your site.
This metric represents the time spent in Input/Output operations (ms).
|
Data Source
Linux: /proc/diskstats or /proc/partitions
User Action
Specific to your site.
This metric represents the number of disk reads from the last collection.
|
Data Source
Linux: /proc/diskstats or /proc/partitions
User Action
Specific to your site.
This metric represents the number of disk reads from the last collection.
|
Data Source
Linux: /proc/diskstats or /proc/partitions
User Action
Specific to your site.
This metric represents the transferred blocks per second.
|
This metric represents the number of blocks (512 bytes) written per second.
|
Data Source
The data sources for this metric include the following:
|
User Action
Specific to your site.
This metric represents the number of blocks (512 bytes) read per second.
Note: On HP UNIX, this metric is named Disk Blocks Transferred (per second).
|
Data Source
The data sources for this metric include the following:
|
User Action
Specific to your site.
This metric displays the name of a disk device.
|
This metric represents disk device busy percentage.
Note: On HP UNIX, this metric is named Device Busy (%).
|
This metric represents the disk reads per second for the specified disk device.
|
Data Source
The data sources for this metric include the following:
|
User Action
Specific to your site.
This metric represents disk utilization percentage.
| Host | Colletion Frequency |
| Windows | Every 15 Minutes |
This metric represents the disk writes per second for the specified disk device.
|
Data Source
The data sources for this metric include the following:
|
User Action
Specific to your site.
The metrics in this category provide information about the summary of disk activity.
This metric displays the longest service time for disk I/Os in milliseconds.
|
This metric displays the maximum disk I/O per second.
|
This metric displays how many disk I/Os are being performed per second.
|
Table 2-5 Metric Summary Table
|
The Disk Device Errors metric category provides the number of errors on the disk device.
Note: These metrics are available on Solaris only.
This metric displays the name of the device.
|
This metric 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.
|
Data Source
The data sources for this metric include the following:
|
User Action
Specific to your site.
This metric 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.
|
Data Source
The data sources for this metric include the following:
|
User Action
Specific to your site.
This metric represents the sum of all errors on the particular device
|
Data Source
The data sources for this metric include the following:
|
User Action
Specific to your site.
This metric represents the error count of network errors encountered. This generally indicates a problem with the network layer
|
Data Source
The data sources for this metric include the following:
|
User Action
Specific to your site.
The File Access System Calls metric category provides information about the usage of file access system calls.
Note: This metric is available on Solaris, HP, and IBM AIX.
This metric represents the number of file system blocks read per second performing direct lookup.
|
Data Source
The data sources for this metric include the following:
|
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.
User Action
None.
This metric represents the number of system iget() calls made per second. iget is a file access system routine.
|
Data Source
The data sources for this metric include the following:
|
User Action
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.
This metric represents the number of file system lookuppn() (pathname translation) calls made per second.
|
Data Source
The data sources for this metric include the following:
|
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.
User Action
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.
This metric 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.
|
Multiple Thresholds
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.
Data Source
The data sources for this metric include the following:
|
User Action
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.
This metric 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.
|
Multiple Thresholds
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.
Data Source
The data sources for this metric include the following:
|
User Action
An alert will be raised if the permissions for a file or directory have changed. User may want to verify the change.
This metric displays the name of this file or directory.
|
This metric displays the current size of this file or directory in kilobytes.
|
This metric fetches the current size of this 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.
|
Multiple Thresholds
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.
Data Source
The data sources for this metric include the following:
|
User Action
If a threshold is exceeded, you may need to take action to adjust the file size or the threshold level.
This metric 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.
|
Table 2-6 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
The data sources for this metric include the following:
|
User Action
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 File Systems configuration metrics list all file systems mounted in the host. Configuration metrics are not available from the All Metrics page of the Cloud Control console.
To view the File Systems configuration metrics:
From the Cloud Control UI, select your Host target type.
Right-click the target type name, and select Configuration, then select Last Collected.
The metrics appear under Latest Configuration.
This metric specifies the available disk space.
|
Data Source
/etc/mtab
User Action
None.
This metric provides the File System capacity in GB.
|
Data Source
/etc/mtab
User Action
None.
Applicable NT only.
|
Data Source
/etc/mtab
User Action
None.
This metric provides the mount location of the file system.
|
Data Source
/etc/mtab
User Action
None.
This metric contains details about the mount options. These could be similar to "rw,intr,largefiles,logging,xattr,onerror=panic."
|
Data Source
/etc/mtab
User Action
None.
This is the device path of host. This can be /dev/hd10opt, Local Disk (C:)
|
Data Source
/etc/mtab
User Action
None.
The Filesystems metrics provide information about local file systems on the computer.
This metric represents the name of the disk device resource.
|
Data Source
The data sources for this metric include the following:
|
User Action
None.
This metric represents the total space (in megabytes) allocated in the file system.
|
Data Source
The data sources for this metric include the following:
|
User Action
None.
This metric represents the percentage of free space available in the file system.
|
Table 2-7 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
The data sources for this metric include the following:
|
User Action
Use the OS du -k command to check which directories are taking up the most space (du -k|sort -rn).
This metric represents the amount (in MB) of free space available in the file system.
|
Table 2-8 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
The data sources for this metric include the following:
|
User Action
Use the OS du -k command to check which directories are taking up the most space (du -k|sort -rn).
This metric displays the total used space on the file system in MB.
|
This metric represents the total space, expressed in megabytes, allocated in the file system.
This metric is available only on Windows.
Data Source
The data source for this metric is GetDiskFreeSpaceEx.
User Action
A high value indicates that the filesystem has very little free space remaining.User might want to manage the free space.
The configuration metrics in this category provide information about the Fault Management Activity (FMA) fault activity. Configuration metrics are not available from the All Metrics page of the Cloud Control console.
To view the FMA Fault Activity configuration metrics:
From the Cloud Control UI, select your Host target type.
Right-click the target type name, and select Configuration, then select Last Collected.
The metrics appear under Latest Configuration.
This metric provides the Fault Automated System Reconfiguration (ASR).
|
Data Source
The data source for this metric includes the following:
|
This metric provides the UUID that was assigned to this fault.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the action that was assigned to this fault.
|
This metric provides the description of the fault.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the Diagnosis Engine that identified the problem.
|
Data Source
The data source for this metric includes the following:
|
This metric indicates whether or not an error has impacted the services provided by the device.
|
Data Source
The data source for this metric includes the following:
|
This metric provides a message identifier that can be used to identify and view an associated knowledge article.
|
Data Source
The data source for this metric includes the following:
|
This metric provides a response to the fault.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the severity of the fault.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the status of the fault.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the timestamp associated with the fault occurrence.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the probability (percentage) that the suspected event is the source of the problem.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the location of the suspected FRU.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the name of the manufacturer of the FRU suspected of causing a fault.
|
This metric provides the name of the FRU suspected of causing a fault.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the part number of the FRU suspected of causing a fault.
|
Data Source
The data source for this metric includes the following:
|
The metric provides the suspect FRU resource.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the revision level of the FRU suspected of causing a fault.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the serial number of the FRU suspected of causing a fault.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the status of the FRU suspected of causing a fault.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the fault class, which represents a hierarchical classification string indicating the type of problem detected, as reported by the fault management subsystem.
|
Data Source
The data source for this metric includes the following:
|
The metrics in this category provide information about FMA SNMP traps.
This metric provides the UUID that was assigned to this problem.
|
This metric provides the status of the fault.
|
This metric provides the code associated with the problem.
|
This section describes the HCA Configuration metrics. Configuration metrics are not available from the All Metrics page of the Cloud Control console.
To view the HCA Configuration metrics:
From the Cloud Control UI, select your Host target type.
Right-click the target type name, and select Configuration, then select Last Collected.
The metrics appear under Latest Configuration.
This metric provides the display name of a channel adapter.
|
Data Source
IS_KEY="TRUE"
Key identifiying a channel adapter.
This metric provides the Channel Adapter name.
|
This metric provides the Channel Adapter Type.
|
This metric provides the firmware version of the HCA.
|
This metric provides the Globally Unique Identifier of the HCA node.
|
This metric provides the hardware version of the HCA.
|
This metric provides the IP Address of the HCA.
|
This metric provides the IP Address 2 of the HCA.
|
This section describes the HCA Port Connections and Configuration metrics. Configuration metrics are not available from the All Metrics page of the Cloud Control console.
To view the HCA Port Connections and Configuration metrics:
From the Cloud Control UI, select your Host target type.
Right-click the target type name, and select Configuration, then select Last Collected.
The metrics appear under Latest Configuration.
The Channel Adapter Display name.
|
This metric displays the HCA port number.
|
The Globally Unique Identifier of the switch to which this HCA port is connected.
|
The port number of the switch to which this HCA port is connected.
|
The HCA Node Globally Unique Identifier.
|
The HCA Port Globally Unique Identifier.
|
The enabled speed of this link (Gbps).
|
The enabled width of this link (for example, 1X or 4X).
|
The supported speed of this link (Gbps).
|
This section describes the HCA Port Errors metrics.
This metric provides the HCA Node Globally Unique Identifier.
|
This metric provides the HCA port number.
|
This metric provides the number of errors of this type in the last collection interval.
|
This metric provides the number of errors of this type in the last collection interval.
|
Table 2-9 Metric Summary Table
|
This metric provides the number of errors of this type in the last collection interval.
|
Table 2-10 Metric Summary Table
|
This metric provides the number of received packets discarded due to constraints.
|
Table 2-11 Metric Summary Table
|
This metric provides the number of errors of this type in the last collection interval.
|
Table 2-12 Metric Summary Table
|
This metric shows the number of errors of this type in the last collection interval.
|
Table 2-13 Metric Summary Table
|
This metric shows the number of errors of this type in the last collection interval.
|
Table 2-14 Metric Summary Table
|
This metric provides the number of errors of this type in the last collection interval.
|
Table 2-15 Metric Summary Table
|
This metric shows the number of errors of this type in the last collection interval.
|
Table 2-16 Metric Summary Table
|
This metric shows the number of errors of this type in the last collection interval.
|
Table 2-17 Metric Summary Table
|
This section describes the HCA Port State metrics.
This metric displays the Globally Unique Identifier of the Host Channel Adapter node.
|
This metric displays the port number of the Host Channel Adapter.
|
This metric displays the active speed of this link (Gbps)
|
This metric displays whether the link speed or width is less than the enabled speed or width respectively, then the link is operating in degraded mode.
|
This metric specifies the active width of this link (for example, 1X or 4X).
|
This metric specifies whether the physical link up or down.
|
This section describes the HCA Port State Alert metrics.
This metric displays the host channel adapter (HCA) globally unique IDs (GUIDs).
|
This metric indicates whether the HCA port is disabled.
|
This metric indicates whether the HCA port if checking or polling for a peer port.
|
The metrics in this category provides information about the performance of the host channel adapter (HCA) port.
The HCA Node Globally Unique Identifier.
|
This metric displays the HCA port number.
|
This metric displays the number of packets received per second.
|
This metric displays the number of bytes received per second.
|
This metric displays the link throughput.
|
This metric displays the number of bytes transmitted per second.
|
This metric category collects IP addresses and aliases from each line of the /etc/hosts file.
Note:
This metric category is supported for Linux, Oracle Solaris on SPARC, Oracle Solaris on x86, IBM AIX on POWER Systems, HP-UX PA-RISC (64-bit), HP-UX Itanium
This metric displays the IP address from the /etc/hosts file.
|
Data Source
/etc/hosts
User Action
Informational only.
The metrics in this category provide information about the status of the IPCS message queues.
This metric provides the identifier for the facility entry.
Data Source
The data source for this metric includes the following:
|
This metric provides the number of megabytes in messages currently outstanding on the associated message queue.
Data Source
The data source for this metric includes the following:
|
This metric provides the maximum number of megabytes allowed in messages outstanding on the associated queue.
Data Source
The data source for this metric includes the following:
|
This metric provides the key that is used as an argument to create the facility entry.
Data Source
The data source for this metric includes the following:
|
This metric provides the name of the group of the creator of the facility entry.
Data Source
The data source for this metric includes the following:
|
This metric provides the login name of the creator of the facility entry.
Data Source
The data source for this metric includes the following:
|
This metric provides the time when the associated entry was created or last changed.
Data Source
The data source for this metric includes the following:
|
This metric provides the name of the group of the owner of the facility entry.
Data Source
The data source for this metric includes the following:
|
This metric provides the identifier of the last process to have received a message from this message queue.
Data Source
The data source for this metric includes the following:
|
This metric provides the identifier of the last process to have sent a message to this message queue.
Data Source
The data source for this metric includes the following:
|
This metric provides the facility access modes.
Data Source
The data source for this metric includes the following:
|
This metric provides the login name of the owner of the facility entry.
Data Source
The data source for this metric includes the following:
|
This metric provides the number of messages in this queue.
Data Source
The data source for this metric includes the following:
|
This metric provides the last time a message was received from this queue.
Data Source
The data source for this metric includes the following:
|
This metric provides the last time a message was sent to this queue.
Data Source
The data source for this metric includes the following:
|
The metrics in this category provide information about the IPCS semaphores status.
This metric provides the identifier for the facility entry.
Data Source
The data source for this metric includes the following:
|
This metric provides the key that is used as an argument to create the facility entry.
Data Source
The data source for this metric includes the following:
|
This metric provides the name of the group of the owner of the facility entry.
Data Source
The data source for this metric includes the following:
|
This metric provides the login name of the owner of the facility entry.
Data Source
The data source for this metric includes the following:
|
This metric provides the access permissions.
Data Source
The data source for this metric includes the following:
|
This metric provides the name of the group of the creator of the facility entry.
Data Source
The data source for this metric includes the following:
|
This metric provides the login name of the creator of the facility entry.
Data Source
The data source for this metric includes the following:
|
This metric provides the time when the associated entry was created or last changed.
Data Source
The data source for this metric includes the following:
|
This metric provide the number of semaphores in the set associated with the semaphore entry.
Data Source
The data source for this metric includes the following:
|
This metric provides the time the last semaphore operation on the set associated with the semaphore entry was completed.
Data Source
The data source for this metric includes the following:
|
The metrics in this category provide information about the status of the IPCS shared memory.
This metric provides the identifier for the facility entry.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the key. that is used as an argument to create the facility entry.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the name of the group of the owner of the facility entry.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the login name of the owner of the facility entry.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the access permissions.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the size (in MB) of segments for shared memory
|
Data Source
The data source for this metric includes the following:
|
This metric provides the time the last attach on the associated shared memory segment was completed.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the name of the group of the creator of the facility entry.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the process ID of the creator of the shared memory entry.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the login name of the creator of the facility entry.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the time when the associated entry was created or last changed.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the time the last detach on the associated shared memory segment was completed.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the process ID of the last process to attach or detach the shared memory segment.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of processes attached to the associated shared memory segment.
|
Table 2-18 Metric Summary Table
|
Data Source
The data source for this metric includes the following:
|
The metric category holds the information about the IO cards in the host, including PCI cards and USBs.
This metric provides the bus type of the IO card.
|
Data Source
lspci
User Action
None.
This metric provides the clock frequency of the IO card.
|
Data Source
lspci
User Action
None.
This metric represents the name of the IO card.
|
Data Source
lspci
User Action
None.
This metric displays the number of IO cards.
|
Data Source
lspci
User Action
None.
This metric represents the IO card revision.
|
Data Source
lspci
User Action
None.
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.
|
Data Source
The data sources for this metric includes the following:
|
User Action
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.
|
Data Source
The data sources for this metric include the following:
|
User Action
None.
This metric represents the number of requests for small memory that failed, that is, requests that were not satisfied.
|
Data Source
The data sources for this metric include the following:
|
User Action
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.
|
Data Source
The data sources for this metric include the following:
|
User Action
None.
This metric represents the amount of memory allocated for oversized memory requests.
|
Data Source
The data sources for this metric include the following:
|
User Action
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.
|
Data Source
The data sources for this metric include the following:
|
User Action
None.
This metric represents the amount of memory, in bytes, the kernel allocated to satisfy large memory requests.
|
Data Source
The data sources for this metric include the following:
|
User Action
None.
This metric represents the amount of memory, in bytes, the kernel allocated to satisfy small memory requests.
|
Data Source
The data source for this metric includes the following:
|
User Action
None.
The metrics in this category provide information about the kernel memory usage.
This metric provides the number of available memory pages.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of desfree pages.
|
Data Source
The data source for this metric includes the following:
|
The metric provides the number of desscan pages.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of contiguous kernel memory pages.
|
Data Source
The data source for this metric includes the following:
|
The metric provides the number of fast scan pages.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of system free memory pages.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of kernel base pages.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the amount (in MB) of the kernel memory.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of lotsfree pages.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of minfree pages.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of kernel memory allocator calls.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of kernel memory allocation pages.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of kernel memory free call pages.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of kernel memory allocator free pages.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of scanned pages.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the total number of pages used by the kernel.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the page size in bytes.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of system free pages.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of locked pages.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the total number of available pages.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of physical pages.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the number of pages scanned per second.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the timestamp for the last data snapshot.
|
Data Source
The data source for this metric includes the following:
|
This metric provides the current size (in MB) of the ZFS Adaptive Replacement Cache (ARC).
|
Data Source
The data source for this metric includes the following:
|
The Load metric provides information about the number of runnable processes on the system run queue. If this is greater than the number of CPUs on the system, then excess load exists.
This metric provides the value of the active logical memory.
|
This metric displays the active memory size in kilobytes.
|
This metric represents the average number of jobs waiting for I/O in the last interval.
|
Data Source
For the following hosts:
|
User Action
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.
|
Data Source
For the following hosts:
|
User Action
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.
|
Data Source
For the following hosts:
|
User Action
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 metric 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.
|
Data Source
The data sources for this metric are Performance Data counters.
User Action
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.
|
Data Source
The data sources for this metric are Performance Data counters.
User Action
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.
|
Data Source
For the following hosts:
|
User Action
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.
This metric represents logical free memory in a system (discounting memory used for file system buffers). Note that this memory can potentially be freed, and may not be available immediately.
|
Data Source
Solaris: vmstat
AIX: libperfstat
User Action
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.
This metric represents the available memory left after the current active memory is consumed out of total memory.
|
Table 2-19 Metric Summary Table
|
Data Source
For the following hosts:
|
User Action
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
This metric represents the amount of free memory in kilobytes.
|
Table 2-20 Metric Summary Table
|
This metric represents free logical memory in a percentage.
|
Data Source
AIX: libperfstat
User Action
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.
This metric represents the maximum of the average service time of all disks. Units are represented in milliseconds.
|
Data Source
For the following hosts:
|
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.
|
Table 2-21 Metric Summary Table
|
Data Source
For the following hosts:
|
User Action
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.
This metric represents the amount of used memory as a percentage of total memory.
|
Table 2-22 Metric Summary Table
|
Data Source
For the following hosts:
|
User Action
For Linux OS, this value might always be close to 100%. See Free Logical Memory (%) for actual free memory that is available for users. Do not take any action based on the value of this metric.
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.
Data Source
The data sources for this metric are Windows Performance counters.
User Action
High transfer rates indicate a memory contention. Adding memory would help.
This metric 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.
|
Table 2-23 Metric Summary Table
|
Data Source
For the following hosts:
|
User Action
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.
This metric 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.
|
Table 2-24 Metric Summary Table
|
Data Source
For the following hosts:
|
User Action
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.
This metric 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.
|
Table 2-25 Metric Summary Table
|
Data Source
For the following hosts:
|
User Action
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.
This metric represents the amount of free swap space available (in KB).
|
Table 2-26 Metric Summary Table
|
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.
|
Table 2-27 Metric Summary Table
|
Data Source
For the following hosts:
|
User Action
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.
For UNIX-based platforms, this metric represents the amount of swapped memory in use for the last interval.
For Windows, this metric represents the amount of page file instance used.
|
Table 2-28 Metric Summary Table
|
This metric represents the total number of processes currently running on the system. This metric checks the number of processes running on the system.
|
Table 2-29 Metric Summary Table
|
Data Source
For the following hosts:
|
User Action
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.
Data Source
Performance Data counters and Windows API GlobalMemoryStatusEx
User Action
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.
This metric represents the total number of users currently logged into the system. This metric checks the number of users running on the system.
|
Table 2-30 Metric Summary Table
|
Data Source
For the following hosts:
|
User Action
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.
This metric represents the percentage of the Active Logical memory.
|
Table 2-31 Metric Summary Table
|
Data Source
For the following hosts:
|
User Action
If this alert is raised, then you must analyze the problem to determine the root cause and resolve the underlying issue.
This metric represents the size in kilobytes of the page file instance used.
This metric is available only on Windows.
Data Source
Performance Data counters and Windows API GlobalMemoryStatusEx.
User Action
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 Monitor metric category 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 Management Repository for each pattern. The user can set a threshold against the number of lines matching this pattern. File rotation will be handled within the given file.
This metric displays the time of the first occurrence of the specified pattern.
|
This metric displays the Perl pattern to be ignored in the log file.
|
This metric displays the time of the last occurrence of the specified pattern.
|
This metric displays the name of the log file.
|
This metric returns the actual content if this file has been specifically registered for content uploading. Otherwise, it returns 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 the Management Repository in EMDROOT/sysman/config/lfm_ifiles file.
|
Data Source
Oracle-provided Perl program that scans files for the occurrence of user-specified Perl patterns.
User Action
None.
This metric returns the number of lines matching the pattern specified in this 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 this log file.
|
Table 2-32 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
Oracle-supplied Perl program monitors the log files for user specified criteria.
User Action
None.
This metric category provides information about Logical Partitioning (LPAR) performance on IBM AIX systems.
This metric represents the amount of CPU utilization as a percentage of total CPU processing power available..
|
This metric represents the percentage of the LPAR's CPU entitlement consumed.
|
This metric represents the percentage of the entitled processing capacity unused while the partition was idle and did not have any outstanding disk I/O request.
|
Table 2-33 Metric Summary Table
|
This metric represents the number of physical processors consumed.
|
Table 2-34 Metric Summary Table
|
This metric represents the percentage of the entitled processing capacity used while executing at the system level (kernel).
|
Table 2-35 Metric Summary Table
|
This metric represents the percentage of the entitled processing capacity used while executing at the user level (application).
|
Table 2-36 Metric Summary Table
|
This metric represents the percentage of the entitled processing capacity unused while the partition was idle and had outstanding disk I/O request(s).
|
Table 2-37 Metric Summary Table
|
The metrics in this category provide information about memory usage.
This metric provides the amount of free memory available in MB.
|
This metric provides the available memory left after the current active memory is consumed out of total memory.
|
This metric provides the total amount of memory in MB.
|
This metric provides the amount of used memory in MB.
|
This metric provides the amount of used memory as a percentage of total memory.
|
This metric provides the current size (in MB) of the ZFS Adaptive Replacement Cache (ARC).
|
The metrics in this category provide information about memory usage.
This metric provides the memory type.
|
This metric provides the restriction or limit (MB) for this memory type (if memory cap is set).
|
This metric provides the memory restriction as a percentage of the total memory.
|
This metric provides the total memory size (MB) of this memory type.
|
The Message and Semaphore Activity metric category provides information about the message and semaphore activity of the host system being monitored.
This metric 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.
|
Data Source
The data sources for this metric include the following:
|
User Action
None.
This metric 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.
|
Data Source
The data sources for this metric include the following:
|
User Action
None.
The metrics in this category provide information about the network datalinks bandwidth. These configuration metrics are not available from the All Metrics page of the Cloud Control console.
To view the Network Datalinks Bandwidth configuration metrics:
From the Cloud Control UI, select your Host target type.
Right-click the target type name, and select Configuration, then select Last Collected.
The metrics appear under Latest Configuration.
This metric provides the datalink name.
|
This metric provides the relative bandwidth priority.
|
This metric provides the differentiated service field.
|
This metric displays the name of the datalink flow.
|
This metric displays the local address for the datalink flow.
|
This metric displays the service specified by the local port.
|
This metric displays the maximum bandwidth of the datalink.
|
This metric displays the remote address for the datalink flow.
|
This metric displays the service specified by the remote port.
|
The metrics in this category provide information about the Network Datalinks performance.
This metric provides the datalink name.
|
This metric provides the number of collisions.
|
This metric provides the number of inbound broadcast octets.
|
This metric provides the number of inbound broadcasts.
|
This metric provides the number of inbound dropped octets.
|
This metric provides the number of inbound drops.
|
This metric provides the number of inbound errors.
|
This metric provides the number of inbound multicast octets.
|
This metric provides the number of inbound multicasts.
|
This metric provides the number of inbound octets.
|
This metric provides the number of inbound packets.
|
This metric provides the number of outbound broadcast octets
|
This metric provides the number of outbound broadcasts.
|
This metric provides the number of outbound dropped octets.
|
This metric provides the number of outbound drops since the last collection.
|
This metric provides the number of outbound errors
|
This metric provides the number of outbound multicast octets.
|
This metric provides the number of outbound multicasts.
|
This metric provides the number of outbound octets.
|
This metric provides the average of the outbound octet rate for this interface.
|
This metric provides the number of outbound packets.
|
This metric provides the link state.
|
This metric category describes the metrics associated with network interfaces.
This metric 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).
|
|
Table 2-38 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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'.
This metric represents the percentage of network bandwidth being used by reading and writing from and to the network for full-duplex network connections.
|
Table 2-39 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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'.
This metric provides the name of the network interface.
|
This metric 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).
|
|
Table 2-40 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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).
|
|
Table 2-41 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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'.
This metric represents the amount of megabytes per second read from the specific interface.
|
|
Table 2-42 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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'.
This metric represents the amount of network bandwidth being used for reading from the network as a percentage of total read capacity.
|
|
Table 2-43 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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'.
This metric 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.
|
Table 2-44 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
It is computed as the sum of Network Interface Input Errors (%) and Network Interface Output Errors (%).
User Action
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'.
This metric 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).
|
Table 2-45 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
It is computed as the sum of Network Interface Read (MB/s) and Network Interface Write (MB/s).
User Action
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'.
This metric represents the amount of megabytes per second written to the specific interface.
The following table shows how often the metric's value is collected.
|
|
Table 2-46 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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'.
This metric represents the amount of network bandwidth being used for writing to the network as a percentage of total read capacity.
|
|
Table 2-47 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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 metrics in this category provide information about the network interfaces bandwidth.
This metric provides the name of the network interface.
|
This metric provides the total network collisions (in percentage) of the network interface since the last collection.
|
This metric provides the average input/output operations over 10 minutes.
|
This metric provides the average percentage of activity over 10 minutes.
|
This metric provides the amount of bandwidth used since the last collection.
|
This metric provides the average input operations over 10 minutes.
|
This metric provide the percentage of input errors on the interface.
|
This metric provides the percentage of input/output errors.
|
This metric provides the average input operations over 10 minutes.
|
This metric category relates to bonded network interface cards. Slave interface cards have the same information as bonded cards.
Name of the bond.
|
Mode of the bonds. This can be balance-alb.
|
Options/properties of the bond. This can be something like "miimon=100 max_bonds=4."
|
Primary slave of the bond. The Network Interface Card which is the primary slave of the bond.
|
This metric category relates to network interface cards, both unbonded and bonded interface cards. Slave interface cards have the same information as bonded cards.
This metric displays the broadcast address of the local area network.
|
Data Source
ifconfig
User Action
None.
This metric displays the default gateway configured for this host.
|
Data Source
ifconfig
User Action
None.
This metric displays a description of the Network Interface Card.
|
Data Source
ifconfig
User Action
None.
This metric represents whether this Network Interface Card (NIC) is configured for dynamic or static ip addresses
|
Data Source
ifconfig
User Action
None.
This metric indicates whether this Network Interface Card (NIC) is a physical NIC.
|
Data Source
ifconfig
User Action
None.
This metric displays the Network interface card's flags.
|
Data Source
ifconfig
User Action
None.
This metric represents the aliases for the host corresponding to this Network Interface Card.
|
Data Source
arp
User Action
None.
This metric provides the IP address associated with this Network Interface Card. This is an IPV4 address.
|
Data Source
ifconfig
User Action
None
This is a comma-separated list of IPV6 addresses.
|
Data Source
ifconfig
User Action
None.
This metric provides the unique address of the Network Interface Card.
|
Data Source
ifconfig
User Action
None.
This is the subnet mask inet address.
|
Data Source
ifconfig
User Action
None.
This metric provides the maximum packet size that to be sent it from this Network Interface Card. This is in bytes.
|
Data Source
ifconfig
User Action
None.
The metrics in this category provide information about the network interfaces performance.
This metric provides the number of collisions.
|
This metric provides the number of inbound drops.
|
This metric provides the number of inbound errors.
|
This metric provides the number of frame errors.
|
This metric provides the number of inbound octets.
|
This metric provides the average of the inbound octet rate for this interface.
|
This metric provides the number of overruns since the last collection.
|
This metric provides the number of inbound packets.
|
This metric provides the name of the interface, unique within the context of the target.
|
This metric provides the name of the interface, unique within the context of the target.
|
This metric displays the interface state transitioned to UP.
|
This metric provides the number of outbound carrier errors.
|
This metric provides the number of outbound drops since the last collection
|
This metric provides the number of outbound errors.
|
This metric provides the number of outbound octets.
|
This metric provides the average of the outbound octet rate for this interface.
|
This metric provides the number of outbound overruns since the last collection.
|
This metric provides the number of outbound packets.
|
This metric provides the link state.
|
The Network Interfaces Summary metric category provides information about all network interfaces.
This metric represents the combined utilization in percentage across all the network interfaces.
|
This metric represents the amount of megabytes per second read from all the network interfaces.
|
This metric represents the percentage in reading utilization across all network interfaces.
|
This metric represents the total I/O rate on all the network interfaces. It is measured as the sum of All Network Interfaces Write Rate (MB/sec) and All Network Interfaces Read Rate (MB/sec).
|
This metric represents the amount of megabytes per second written to all the interfaces.
|
This metric represents the percentage in writing utilization across all network interfaces.
|
The metrics in this category provide information about the new disk activity summary IO.
The metrics in this category provide information about the new disk activity summary IO.
The metrics in this category provide information about new CPU usage.
This metric provides the CPU ID.
|
This metric provides the number of context switches per second.
|
This metric provides the percentage of IO waiting time.
|
This metric provides the number of interrupts per second.
|
This metric provides the percentage of the sort interrupts time.
|
This metric provides the percentage of system time.
|
Table 2-48 Metric Summary Table
|
This metric provides the usage restriction or cap.
|
This metric provides the usage restriction as a percentage of the total CPU usage.
|
This metric provides the percentage of user time.
|
Table 2-49 Metric Summary Table
|
This metric provides the amount of CPU utilization as a percentage of total CPU processing power available.
|
This metric provides the percentage of time that the CPU was idle and the system did not have an outstanding disk I/O request.
|
This metric provides the percentage of hard interrupts.
|
The metrics in this category provide information about new paging activity.
This metric provides the number of pages put on the freelist per second by the page stealing daemon.
|
This metric provides the number of page-in requests per second.
|
This metric provides the page-out requests per second.
|
This metric provides the number of pages scanned per second by the page stealing daemon.
|
Table 2-50 Metric Summary Table
|
This metric provides the number of paged-in pages per second.
|
Table 2-51 Metric Summary Table
|
This metric provides the number of paged-out pages per second.
|
Table 2-52 Metric Summary Table
|
This metric provides the number of page faults from software lock requests.
|
This metric provides the percentage of igets with page flushes.
|
This metric category contains the operating summary information. There will be one row per host.
This metric provides the OS address length. This is either 32 bit or 64 bit.
|
Data Source
uname -a
User Action
None.
This metric provides the base version of the OS.
|
User Action
None.
This metric displays the current OS run level.
|
This metric indicates if the hose is a member database machine. When the host is a member database machine, this column has a value of 1.
|
Data Source
uname -a
User Action
None.
This metric indicates if it is an Exalogic member.
|
Default Run level of the OS running on the host. Whenever the OS is booted, it will be booted to this run level.
|
Data Source
uname -a
User Action
None.
This metric displays the distributor version.
|
This metric specifies the maximum process virtual memory (MB).
|
This metric represents Maximum swap space available for the OS.
|
Data Source
uname -a
User Action
None
This metric represents the name of the OS.
|
Data Source
/etc/enterprise-release for OEL
/etc/redhat-release for redhat
/etc/UnitedLinux-release
/etc/SuSE-release
User Action
None.
This metric represents the platform id number.
|
Data Source
uname -a
User Action
None.
This metric specifies the version ID of the platform.
|
This metric specifies the time zone.
|
This metric displays the timezone delta between UTC and current timezone
| Target Version | Collection Frequency |
| All Versions | Every 24 Hours |
This metric specifies the time zone region.
|
This metric provides the latest update level of this OS.
|
Data Source
uname -a
User Action
None.
This metric stores the information about OS components, including Patches, Bundles, and Packages.
Description of the component
|
Data Source
/bin/rpm
User Action
None.
Installation date of the component.
|
Data Source
/bin/rpm
User Action
None.
Name of the OS component.
|
Data Source
/bin/rpm
User Action
None.
Type of OS components. This can be Patch, Bundle, Package.
|
Data Source
/bin/rpm
User Action
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.
|
Data Source
/bin/getconf, ulimit
This is the source of the property info. This can be similar to /sbin/sysctl or /usr/bin/getconf.
|
Data Source
/bin/getconf , ulimit
This metric contains details of all the OS Registered Software.
Any vendor description for the software.
|
Data Source
/bin/rpm
User Action
Informational only.
ID of Software installed in the host. Only applicable for NT/Windows.
|
Data Source
/bin/rpm
User Action
Informational only.
Installation date of the software.
|
Data Source
/bin/rpm
User Action
Informational only.
The location where the software is installed.
|
Data Source
/bin/rpm
User Action
Informational only.
Installation or distribution source of the installed product. For example, the package name, bundling application, or distro.
|
Data Source
/bin/rpm
User Action
Informational only.
Name of installed software.
|
Data Source
/bin/rpm
User Action
Informational only.
Vendor who provided the software
|
Data Source
/bin/rpm
User Action
Informational only.
Anything related to software
|
Data Source
/bin/rpm
User Action
Informational only.
Any vendor description for the software.
|
Data Source
/bin/rpm
User Action
Informational only.
This metric represents the Solaris zone name in which the product is installed.
|
Data Source
/bin/rpm
User Action
Informational only.
Parent ID of the installed product. Applicable to the Sun Service Tag product taxonomy
|
Data Source
/bin/rpm
User Action
Informational only.
Descriptive parent name of the installed product. Applicable to the Sun Service Tag product taxonomy
|
Data Source
/bin/rpm
User Action
Informational only.
The metrics in this category provide information about the operating system service status.
This metric provides the Fault Management Resource Identifier (FMRI).
|
Data Source
The data source for the metrics in this category includes the following:
|
This metric provides the contract identifier.
|
Data Source
The data source for the metrics in this category includes the following:
|
This metric provides the name and location of the error log file.
|
Data Source
The data source for the metrics in this category includes the following:
|
This metric indicates whether this service is listening on an open port. Valid values are TRUE or FALSE.
|
This metric provides the next service state.
|
Data Source
The data source for the metrics in this category includes the following:
|
This metric specifies if the service is enabled.
|
Data Source
The data source for the metrics in this category includes the following:
|
This metric provides the service state.
|
Table 2-53 Metric Summary Table
|
Data Source
The data source for the metrics in this category includes the following:
|
This metric category 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.
|
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".
|
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.
|
Maximum size of the file a process can create. Number will be in 512 bytes (one block).
|
This number represents maximum number of files that can be opened at a time.
|
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.
|
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.
|
This metric category provides information about Solaris Engineered Systems. These configuration metrics are not available from the All Metrics page of the Cloud Control console.
To view the Oracle Engineered Systems configuration metrics:
From the Cloud Control UI, select your Host target type.
Right-click the target type name, and select Configuration, then select Last Collected.
The metrics appear under Latest Configuration.
Note:
These metrics are supported for Solaris hosts only.
Configuration history is turned off for all these metrics but configuration comparison is available.
This metric displays the Oracle Engineered System Identifier. This is the serial number of the Engineered System specified during production.
|
Data Source
rack/serial_number property from the oes/id Oracle Solaris Service Management Facility (SMF) service.
User Action
Informational only.
This metric displays the Oracle Engineered system name and optionally the build ID.
|
Data Source
oes/type and configuration/build properties from the oes/id SMF service.
User Action
Informational only.
This metric can display the hardware or software version, revision or other details associated with this Engineered system.
|
Data Source
oes/node, configuration/name and configuration/domain_type properties from the oes/id SMF service.
User Action
Informational only.
The Paging Activity metric category provides the amount of paging activity on the system.
This metric displays the number of active pages.
|
This metric displays the number of active pages per second.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
Informational only.
This metric 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).
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
Informational only.
This metric 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.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
Informational only.
This metric displays the number of clean inactive pages.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
Informational only.
This metric displays the number of clean inactive page per second..
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
Informational only.
This metric displays the number of dirty inactive pages.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
Informational only.
This metric 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).
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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.
|
|
Table 2-54 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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.
|
Table 2-55 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
Informational only.
This metric 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.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
Informational only.
This metric represents the scan rate is the number of pages per second scanned by the page stealing daemon.
|
Table 2-56 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
Informational only.
The metrics in this category provide information about the process IPCS usage.
This metric provides the IPCS identifier.
|
This metric provides the type of interprocess communication (IPC).
|
This metric provides the process ID.
|
The Top Processes metric category 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.
This metric represents the command and all its arguments.
Data Source
For the following hosts:
|
User Action
None.
This metric represents the CPU utilization time in seconds.
Data Source
For the following hosts:
|
User Action
None.
This metric represents the percentage of CPU time consumed by the process.
Data Source
For the following hosts:
|
User Action
None.
This metric represents the percentage of memory consumed by the process.
Data Source
For the following hosts:
|
User Action
None.
This metric represents the number of kilobytes of physical memory being used.
Data Source
For the following hosts:
|
User Action
None.
This metric displays the process identifier.
Data Source
For the following hosts:
|
User Action
None.
This metric represents the user name that owns the process, that is, the user ID of the process being reported on.
Data Source
For the following hosts:
|
User Action
None.
This metric represents the total size of the process in virtual memory in kilobytes (KB).
Data Source
For the following hosts:
|
User Action
None.
The Process, Inode, File Tables Stats metric category provides information about the process, inode, and file tables status.
This metric 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.
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric 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.
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric 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.
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric 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.
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric 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.
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric represents the number of allocated disk quota entries.
|
Table 2-57 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric provides the total number of pseudo-terminals used by the system.
|
This metric provides the number of queued RT signals.
|
Table 2-58 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric provides the number of allocated super block handlers.
|
Table 2-59 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric represents the current size of the system file table.
|
Table 2-60 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric represents the Percentage Of Allocated Disk Quota Entries against the maximum number of cached disk quota entries that can be allocated.
|
Table 2-61 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric represents the Percentage Of Allocated Super Block Handlers against the maximum number of super block handlers that Linux can allocate.
|
Table 2-62 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric represents the percentage of queued RT signals.
|
Table 2-63 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric represents the percentage of used file handles against the maximum number of file handles that the Linux kernel can allocate.
|
Table 2-64 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric 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.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric represents the current size of the inode table.
|
Table 2-65 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric represents the current size of the process table.
Metric Summary
The following table shows how often the metric's value is collected.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric provides the size of the system file table.
|
The metrics in this category provide information about processor group usage.
This metric provides the hardware load as a percentage.
|
This metric provides the percentage of time that no software threads ran on CPUs in the processor group.
|
This metric displays the ID associated with the processor group.
|
This metric provides the software load as a percentage.
|
This metric provides the percentage of time that software threads ran in system mode on CPUs in the processor group during interval.
|
The metrics in this category provide information about the processor set usage.
This metric displays the current number of processors.
|
This metric provides name of the processor set.
|
This metric provides the percentage of time that the CPU was idle and the system did not have an outstanding disk I/O request.
|
This metric provides the percentage of process time.
|
This metric provides the percentage of time the process has spent in system mode.
|
The metrics in this category provide information about the processor set zone usage.
This metric provides the name of the processor set.
|
This metric provides the name of the zone.
|
This metric provides the amount of CPU time used by the processor set.
|
This metric provides the percentage of CPU time used by the processor set.
|
This metric provides the processor set schedulers.
|
This metric provides the number of shares allocated to the processor set.
|
This metric provides the percentage of shares allocated to the processor set.
|
This metric provides the percentage of used allocated shares.
|
This metric provides the restriction or cap.
|
The Program Resource Utilization metric category 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 displays the name of the user running the given process.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric represents the maximum CPU time accumulated by the most active process matching the {program name, owner} key value criteria.
|
Table 2-66 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric displays the identifier of the process that has accumulated the most CPU time matching the {program name, owner} key value criteria.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric represents the maximum percentage of CPU utilized by a single process matching the {program name, owner} key value criteria since last scan.
|
Table 2-67 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric 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.
|
Table 2-68 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric 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.
|
Table 2-69 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric provides the identifier of the process with the maximum resident memory occupied by a single process matching the {program name, owner} key value criteria.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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-70 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric provides the name of the program.
|
This metric represents the total CPU time accumulated by all active process matching the {program name, owner} key value criteria.
|
Table 2-71 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric represents the percentage of CPU time utilized by all active process matching the {program name, owner} key value criteria since last collection.
|
Table 2-72 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric category provides the status of the Reliable Datagram Sockets (RDS protocol layer.
This metric indicates whether the host can be contacted using the RDS ping utility.
|
Table 2-73 Metric Summary Table
|
This section provides details on the Windows Services metrics.
This metric displays a unique identifier of the service that provides an indication of the functionality that is managed.
|
This metric displays a fully qualified path to the service binary file that implements the service. For example, C:\Windows\Oracle\monitor.sys.
|
This metric provides a description of the object
|
This metric provides the display name of the service. This string has a maximum length of 256 characters. The name is case-preserved in the Service Control Manager
|
This metric displays the process identifier of the service.
|
This metric displays the start mode of the Windows base service. Possible values are Boot, System, Auto, Manual, and Disabled.
|
This metric provides an account name under which a service runs. Depending on the service type, the account name may be in the form of DomainName\Username
|
This metric specifies if the service started. Possible values are true and false.
|
This metric displays the current state of the base service.The following are the possible values:
Stopped
Start Pending
Stop Pending
Running
Continue Pending
Pause Pending
Paused
Unknown
|
Current status of the object. This includes both operational and non-operations status provided by the service. The following are the possible values:
OK
Error
Degraded
Unknown
Pred Fail
Starting
Stopping
Service
|
This section provides information about the metric categories and metrics relating to Solaris Virtualization technologies.
These metrics support the following Solaris Virtualization technologies:
Zones
Non-global zone
Global zone
Virtual Box
Solaris running as Guest OS
Oracle VM for x86
domU
Oracle VM for SPARC (Logical Domains (LDOMs))
Guest
Control
I/O
Services
Root
Solaris Virtualization metrics use Oracle Certified monitoring templates to enable or disable scheduled collections. By default these metrics are disabled and are not collected.
For more information about monitoring templates, see the Oracle Enterprise Manager Cloud Control Administrator's Guide.
To enable the Solaris Virtualization configuration metrics:
This metric category provides information about the Solaris OVM for SPARC configuration metrics.
These configuration metrics are not available from the All Metrics page of the Cloud Control console.
To view the Solaris OVM for SPARC configuration metrics:
From the Cloud Control UI, select your Host target type.
Right-click the target type name, and select Configuration, then select Last Collected.
The metrics appear under Latest Configuration.
This metric displays a number that represents available CPU count for this domain.
|
Data Source
The ncpu field retrieved using the command-line interface for the Logical Domains Manager utility (ldm(1M)).
User Action
Informational only
This metric displays a list of the roles that a logical domain can perform.
|
Data Source
DOMAINROLE field retrieved using the virtinfo(1M) utility.
User Action
Informational only
This metric displays the domain name from the ldm (1M) utility or DOMANUUID field retrieved using the virtinfo (1M) utility.
|
Data Source
Domain Name from the ldm(1M) utility or DOMAINUUID field retrieved using the virtinfo(1M) utility.
User Action
Informational only
This metric displays the comma separated list of all IO types used by the domain.
|
Data Source
Comma separated list of unique IO types retrieved using the ldm(1M) utility.
User Action
Informational only
This metric displays 1 or 0. 1 indicates if any of the virtual switch (VSW) or virtual network (VNET) network devices have an maximum transmission unit (MTU) greater than 1500.
|
Data Source
Check based on the MTU value retrieved by the ldm(1M) utility.
User Action
Informational only
This metric specifies the maximum number of cores that are permitted to be assigned to a domain.
|
Data Source
max-cores property retrieved using the ldm(1M) utility.
User Action
Informational only
This metric displays the type of the migration mode. It can be generic or native.
|
Data Source
Generic or native value from the cpu-arch property retrieved using the ldm(1M) utility.
User Action
Informational only
This metric displays the chassis serial number retrieved by the virtinfo(1M) utility.
|
Data Source
DOMAINCHASSIS field retrieved using the virtinfo(1M) utility.
User Action
Informational only
This metric specifies that CPU cores are allocated to a domain rather than to virtual CPUs.
|
Data Source
whole-core property retrieved using the ldm (1M) utility.
User Action
Informational only
This metric category provides information about the Solaris Zones Configuration metrics.
These configuration metrics are not available from the All Metrics page of the Cloud Control console.
To view the Solaris Zones configuration metrics:
From the Cloud Control UI, select your Host target type.
Right-click the target type name, and select Configuration, then select Last Collected.
The metrics appear under Latest Configuration.
This metric displays the system-assigned processor set ID for the processor set used by the zone.
|
Data Source
cpu.sys_id property for used pset retrieved by the pooladm(1M) command.
User Action
Informational only
This metric displays the value to control an absolute limit on the amount of CPU resources that can be consumed by a zone.
|
Data Source
capped-cpu/ncpus property retrieved by the zonecfg(1M) utility.
User Action
Informational only
This metric displays the current number of CPUs in the processor set used by the zone.
|
Data Source
pset.size property for used pset retrieved by the pooladm(1M) command.
User Action
Informational only
This metric displays the host name of a zone.
|
Data Source
hostOSD::getHostName()
User Action
Informational only
This metric displays the IP type used by the zone. There are two IP types available for non-global zones:
shared-IP
exclusive-IP
|
Data Source
zoneadm(1M).
User Action
Informational only
This metric displays the value to control lock memory used by processes in the non-global zone.
|
Data Source
The capped-memory/locked property retrieved by the zonecfg(1M) utility.
User Action
Informational only
This metric displays the limits on the number of processors that can be allocated to a processor set used by a zone.
|
Data Source
pset.max property for used pset retrieved by the pooladm(1M) command.
User Action
Informational only
This metric displays the value to control maximum number of processes in the non-global zone.
|
Data Source
max-processes property retrieved by the zonecfg(1M) utility.
User Action
Informational only
This metric displays the value specifying the number of the system's processors that should be dedicated to a non-global zone while it is running.
|
Data Source
dedicated-cpu/ncpus property retrieved by the zonecfg(1M) utility.
User Action
Informational only
This metric displays the value to regulate physical memory consumption used by processes in the non-global zone.
|
Data Source
capped-memory/physical property retrieved by the zonecfg(1M) utility.
User Action
Informational only
This metric displays the processor set name within the resource pool currently used by a zone.
|
Data Source
pset name for used pool name retrieved by the pooladm(1M) command.
User Action
Informational only
This metric displays the resource pool name used by a zone.
|
Data Source
pool property retrieved by the zonecfg(1M) utility.
User Action
Informational only
This metric displays a value to control swap space used by the non-global zone.
|
Data Source
capped-memory/swap property retrieved by the zonecfg(1M) utility.
User Action
Informational only
This metric displays the brand of the zone.
|
Data Source
zoneadm(1M).
User Action
Informational only
This metric displays the name of the zone.
|
Data Source
zoneadm(1M)
User Action
Informational only
This metric lists the privileges for this non-global zone. In the nonglobal zone, processes are restricted to a subset of privileges. Privilege restriction prevents a zone from performing operations that might affect other zones. The set of privileges limits the capabilities of privileged users within the zone.
|
Data Source
limitpriv property retrieved by the zonecfg(1M) utility.
User Action
Informational only
This metric displays the status of the zone, such as running, configured, ready, and installed.
|
Data Source
zoneadm(1M).
User Action
Informational only
This metric displays the zone universally unique identifier (UUID), zone name, or unique identifier from the smbios(1M) utility.
|
Data Source
Zone UUID, zone name, or UUID from the smbios utility.
zoneadm(1M) or smbios(1M) UUID
User Action
Informational only
This metric category provides information about the Solaris Zones SMF Services Configuration metrics.
These configuration metrics are not available from the All Metrics page of the Cloud Control console.
To view the Solaris Zones SMF Services configuration metrics:
From the Cloud Control UI, select your Host target type.
Right-click the target type name, and select Configuration, then select Last Collected.
The metrics appear under Latest Configuration.
This metric displays the name of the current zone.
|
This metric displays the Fault Management Resource Identifier (FMRI) column for each Oracle Solaris Service Management Facility (SMF) service in all running zones except for services in a disabled state.
|
Data Source
The svcs(1) command used with the zlogin(1) command.
User Action
Informational only
This metric displays the STATE column for each SMF service in all running zones except for services in a disabled state.
|
Data Source
The svcs(1) command used with the zlogin(1) command.
User Action
Informational only
This metric displays the zone UUID, zone name, or unique identifier from the smbios(1M) utility.
|
Data Source
zone UUID, zone name or UUID from smbios.
zoneadm(1M) or smbios(1M) UUID
User Action
Informational only
This metric category provides information about the Virtualization Technologies metrics. It collects generic details about virtualization technologies found on the system.
These configuration metrics are not available from the All Metrics page of the Cloud Control console.
To view the Virtualization Technologies configuration metrics:
From the Cloud Control UI, select your Host target type.
Right-click the target type name, and select Configuration, then select Last Collected.
The metrics appear under Latest Configuration.
This metric can display the hardware or software version, revision, or any other information associated with the selected virtualization technology.
|
Data Source
ldm(1M), smbios(1M), zoneadm(1M)
User Action
Informational only
This metric can display a UUID, or another unique identifier preceded by the Virtualization Technology prefix.
|
Data Source
Prefixed with virtualization technology name UUID from the smbios(1M) utility, zone name or UUID, Oracle VM for SPARC domain UUID or domain name.
smbios(1M), zoneadm(1M), virtinfo(1M), ldm(1M)
User Action
Informational only
This metric category provides information about the Storage Area Network configuration metrics. Configuration metrics are not available from the All Metrics page of the Cloud Control console.
To view the Storage Area Network configuration metrics:
From the Cloud Control UI, select your Host target type.
Right-click the target type name, and select Configuration, then select Last Collected.
The metrics appear under Latest Configuration.
Note:
These metrics are supported for Linux and Solaris hosts only.
By default, these metrics are disabled and will not be collected.
Storage Area Network metrics use Oracle Certified monitoring templates to enable or disable scheduled collections. By default these metrics are disabled.
For more information about monitoring templates, see the Oracle Enterprise Manager Cloud Control Administrator's Guide.
To enable these configuration metrics:
This metric specifies whether the Fibre Channel protocol is supported.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric specifies whether Internet Small Computer System Interface (iSCSI) protocol is supported.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the name of the multipath software.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric subcategory provides information about the Storage Area Network (SAN) devices.
This metric displays the World Wide Port Name (WWPN) assigned to a port in a Fibre Channel fabric.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the name of the SAN fabric. The SAN fabric enables any-server-to-any-storage device connectivity through the use of Fibre Channel switching technology.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the maximum frame size for the fibre channel frame.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the model description of the HBA.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the World Wide Node Name (WWNN) assigned to a node in a Fibre Channel fabric.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the port ID of the HBA.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric indicates the status of the HBA.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the type of Fibre Channel port.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the speed of the HBA.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the classes supported by the HBA.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the speeds supported by the HBA.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the bind type of the target ID and specifies the method of binding for each port.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the manufacturer or vendor of the HBA.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric subcategory provides information about the Storage Area Network (SAN) devices.
This metric displays the type of property name such as IQN (iSCSI Qualified Name).
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the value of the property name.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric category provides information about the Storage Area Network (SAN) devices. These are configuration metrics and cannot be viewed from the All Metrics page in the Cloud Control UI.
Note:
These metrics are supported for Linux and Solaris hosts only.
This metric displays the disk path to the SAN device.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the Logical Unit Number (LUN). The LUN is a disk presented to a computer system by a storage array.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the unique ID assigned to a LUN.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the SAN protocol.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the path to the pseudo device used by multipathing to facilitate the sharing and balancing of I/O operations across all of the available I/O paths.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the iSCSI Qualified Name (IQN) of the storage server.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the World Wide Node Name (WWNN) assigned to the storage server.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the World Wide Port Name (WWPN) of the storage server.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric displays the vendor or manufacturer of the SAN device.
|
Data Source
The data sources for the metrics in this category include the following:
|
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.
This metric represents the total storage allocated to Oracle databases from Automatic Storage Management (ASM) instances on the host.
|
User Action
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 represents the number of metric collection errors attributed to the storage related metrics of the Automatic Storage Management (ASM) targets on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the storage overhead of Automatic Storage Management (ASM) targets on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the storage available in Automatic Storage Management (ASM) targets on the host for allocating to databases.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the total free storage available in the databases on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the metric collection errors of storage related metrics of databases on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the total free storage available in the databases on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the storage allocated from the total disk storage available on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the storage that is available for allocation in disks on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the total number of storage related metric collection errors of the host target.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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).
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the total free storage in all distinct local file systems on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the total used space in all distinct local file systems on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the total number of Automatic Storage Management (ASM) instances, the storage data of which was used in computing storage summary of this host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the total number of databases, the storage data of which was used in computing storage summary of this host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the storage metric mapping issues on the host excluding the unmonitored server mapping errors.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the total number of Automatic Storage Management (ASM) instances on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the total number of databases on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the total storage allocated from the host-visible storage available on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the free storage available from the total allocated storage on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the overhead associated with storage on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the total unallocated storage on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the total storage used in the file systems and databases on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the total number of storage mapping issues that result from unmonitored Network File Systems (NFS) servers.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the total storage allocated from the volumes available on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the storage overhead in the volumes on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the storage available for allocation in the volumes on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the total free space available in all distinct writeable NFS mounts on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 represents the storage used in all writeable NFS mounts on the host.
|
Data Source
These metrics are available on the Linux and Solaris hosts.
User Action
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 category is used to decide if the OS being monitored is supported. It's 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 or 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.
Data Source
Not available
User Action
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 category provides the status of the swap memory on the system.
This metric displays the name of the swap file.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
This metric represents the number of 1K blocks in the swap area that is not allocated.
|
Table 2-74 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
The data sources for the metrics in this category include the following:
|
User Action
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.
This metric represents the size of the swap file.
|
Data Source
The data sources for the metrics in this category include the following:
|
User Action
None.
The metrics in this category provide information about swap usage.
This metric provides the amount of free swap space.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric provides the free swap space as a percentage of the total swap space.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric provides the total amount of swap space.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric provides the amount of used swap space.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric provides the amount of used swap space as a percentage of the total swap space.
|
Data Source
The data sources for the metrics in this category include the following:
|
The Switch/Swap Activity metric category displays the metric reports on the system switching and swapping activity.
This metric displays the number of process context switches per second
|
Table 2-75 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
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.
User Action
None.
This metric represents the number of 512-byte units transferred for swapins per second.
|
Table 2-76 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
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.
User Action
None.
This metric represents the number of 512-byte units transferred for swapouts per second.
|
Table 2-77 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
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.
User Action
None.
This metric represents the number of process swapins per second.
|
Table 2-78 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
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.
User Action
None.
This metric represents the number of process swapouts per second.
|
Table 2-79 Metric Summary Table
|
Data Source
The data sources for the metrics in this category include the following:
|
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.
User Action
None.
The System Calls metric category provides statistics about the system calls made over a five-second interval.
This metric represents the number of characters transferred by read system calls (block devices only) per second.
Data Source
The data sources for the metrics in this category include the following:
|
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.
User Action
None.
This metric represents the number of characters transferred by write system calls (block devices only) per second.
Data Source
The data sources for the metrics in this category include the following:
|
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.
User Action
None.
This metric represents the number of exec() system calls made per second.
Data Source
The data sources for the metrics in this category include the following:
|
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.
User Action
None.
This metric represents the number of fork() system calls made per second.
Data Source
The data sources for the metrics in this category include the following:
|
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.
User Action
None.
This metric represents the number of read() system calls made per second.
Data Source
The data sources for the metrics in this category include the following:
|
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.
User Action
None.
This metric represents the number of system calls made per second. This includes system calls of all types.
Data Source
The data sources for the metrics in this category include the following:
|
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.
User Action
None.
This metric represents the number of write() system calls made per second.
Data Source
The data sources for the metrics in this category include the following:
|
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.
User Action
None.
The metrics in this category provide information about system load.
This metric provides the total number of CPU cores.
|
This metric provides the total number of processes.
|
The metric provides the total number of users.
|
This metric provides the average number of processes in memory and subject to be run in the last interval. This metric checks the run queue.
|
This metric provides the average number of processes in memory per core and subject to be run in the last interval. This metric checks the run queue.
|
This metric provides the average number of processes in memory and subject to be run in the last interval. This metric checks the run queue.
|
This metric provides the average number of processes in memory per core and subject to be run in the last interval. This metric checks the run queue.
|
This metric represents the average number of processes in memory and subject to be run in the last interval. This metric checks the run queue.
|
The metrics in this category provide information about system times.
This metric provides the system's last boot time.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric provides the current system running time (in minutes) since the last time the system was started.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric provides the current date and time of the system.
|
Data Source
The data sources for the metrics in this category include the following:
|
This metric category provides information about the disk space usage.
This metric displays the total percentage of free disk space across all local file systems.
|
Table 2-80 Metric Summary Table
|
This metric displays the total disk size (in MB) across all local file systems.
|
Data Source
For the following hosts:
|
User Action
None.
This metric displays the total amount of free disk space (in MB) across all local file systems.
|
Table 2-81 Metric Summary Table
|
This metric represents the total amount of disk space used (in MB) across all local file systems.
|
Data Source
For the following hosts:
|
User Action
None.
This metric displays the total percentage of utilized disk across all local file systems
|
Data Source
For the following hosts:
|
User Action
None.
This metric reports TTY device activity.
This metric represents the number of received incoming character interrupts per second.
|
Data Source
For the following hosts:
|
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.
User Action
None.
This metric represents the input characters processed by canon() per second.
|
Data Source
For the following hosts:
|
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.
User Action
None.
This metric represents the modem interrupt rate.
|
Data Source
For the following hosts:
|
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.
User Action
None.
This metric represents the number of transmit outgoing character interrupts per second.
|
Data Source
For the following hosts:
|
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.
User Action
None.
This metric represents the number of output characters per second.
|
Data Source
For the following hosts:
|
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.
User Action
None.
This metric represents the raw input characters per second.
|
Data Source
For the following hosts:
|
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.
User Action
None.
The Users metric category provides information about the users currently on the system being monitored.
This metric represents the number of times a user with a certain user name is logged on to the host target.
|
Table 2-82 Metric Summary Table
|
Data Source
For Solaris, HP, Linux, HP Tru64, and IBM AIX, the number of times a user is logged on is obtained from the OS w command.
For Windows, the source of information is Windows API.
User Action
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 Oracle 9i Management Agent's UDE functionality.
This metric contains a value if the value type is NUMBER. Otherwise, the value is "", if the value is STRING.
Data Source
User defined script.
User Action
None.
This metric category displays information about Virtualization configuration metrics. The value of the collected metrics depends on the platform.
The following properties will be collected for Solaris platforms. The collections vary depending on the type of virtualization technology implemented.
| Property Name | Property Value | Description |
|---|---|---|
|
Virtual |
Yes No Unknown |
Indicates whether this host is running on physical or virtual hardware |
|
Virtual Processors |
Site specific |
Indicates the number of allocated virtual processors |
|
Zone Names |
List of all zone names (for global zone Non global name |
Provides a list of all the zone names for the global zone or else provides the nonglobal name. |
|
Logical Domains Manager |
Site specific |
Indicates the version number of the Logical Domain Manager |
|
Domain Names |
Site specific |
Provides a comma-separated Domain Names list |
|
dedicated-cpu |
True False |
Uses the |
|
capped-cpu |
True False |
Uses the |
|
ncpus |
Site specific |
Indicates the number or range of CPUs |
|
Pool Name |
Site specific |
Pool name |
|
pset.min |
Site specific |
Indicates the minimum number of CPUs for this processor set |
|
pset.max |
Site specific |
Indicates the maximum number of CPUs for this processor set |
|
cpu.sys_id |
Site specific |
Indicates the CPU sys_id |
|
Pool name list |
Site specific |
Provides a list of pool names |
|
Pset name list |
Site specific |
Provides a list of processor sets |
The following properties will be collected for IBM AIX:
| Version | Property Name | Property Value |
|---|---|---|
|
5.3 - 6.0 |
Virtual |
Yes No Unknown |
|
5.3 - 6.0 |
Node Name |
Site specific |
|
5.3 - 6.0 |
Partition Name |
Site specific |
|
5.3 - 6.0 |
Partition Number |
Site specific |
|
5.3 - 6.0 |
Type |
Site specific |
|
5.3 - 6.0 |
Mode |
Site specific |
|
5.3 - 6.0 |
Entitled Capacity |
Site specific |
|
5.3 - 6.0 |
Partition Group-ID |
Site specific |
|
5.3 - 6.0 |
Shared Pool ID |
Site specific |
|
5.3 - 6.0 |
Online Virtual CPUs |
Site specific |
|
5.3 - 6.0 |
Active Physical CPUs in system |
Site specific |
|
5.3 - 6.0 |
Active CPUs in Pool |
Site specific |
|
5-3 - 6.1 and later |
WPAR Key |
Site specific |
|
5-3 - 6.1 and later |
WPAR Configured ID |
Site specific |
|
5-3 - 6.1 and later |
WPAR Maximum Logical CPUs |
Site specific |
|
5-3 - 6.1 and later |
WPAR Maximum Virtual CPUs |
Site specific |
|
5-3 - 6.1 and later |
WPAR Percentage CPU Limit |
Site specific |
The following properties will be collected for Microsoft Windows:
| Property Name | Property Value | Description |
|---|---|---|
|
Virtual |
Yes No Unknown |
Indicates whether this host is running on physical or virtual hardware |
|
Model |
Site specific |
Indicates the model details such as HVM domU |
|
Virtual Machine |
Site specific |
Indicates the type of virtual machine such as Xen |
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.
This metric displays a 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.
|
Data Source
Windows Management Instrumentation (WMI)
User Action
None.
This is the time at which point the metric scanned through the event logs. This metric is available only on Windows.
|
Data Source
Windows Management Instrumentation (WMI)
User Action
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 for Windows only.
|
Data Source
Windows Management Instrumentation (WMI)
User Action
None.
This metric provides the name for the event log record.
|
Data Source
Windows Management Instrumentation (WMI)
User Action
None.
This metric provides the record number for the event log record.
|
Data Source
Windows Management Instrumentation (WMI)
User Action
None.
This metric provides the name of the software that logs the event.
|
Data Source
Windows Management Instrumentation (WMI)
User Action
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.
|
Table 2-83 Metric Summary Table
|
Data Source
Windows Management Instrumentation (WMI)
User Action
None.
This metric displays the seriousness of the event. Possible values are: Warning and Error.
This metric is available for Windows only.
|
Table 2-84 Metric Summary Table
|
Multiple Thresholds
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.
Data Source
WMI Operating System Classes
User Action
None.
The metrics in this category provide information about ZFS ARC Cache usage.
This metric provides the number of demand data misses per second.
|
Data Source
The data source for the metrics in this category include the following:
|
This metric provides the percentage of demand data misses.
|
Data Source
The data source for the metrics in this category include the following:
|
This metric provides the current size of the ZFS metadata.
|
Data Source
The data source for the metrics in this category include the following:
|
This metric provides the percentage size of the ZFS metadata.
|
Data Source
The data source for the metrics in this category include the following:
|
This metric provides the number of read misses per second.
|
Data Source
The data source for the metrics in this category include the following:
|
This metric provides the percentage of read misses.
|
Data Source
The data source for the metrics in this category include the following:
|
This metric provides the number of metadata misses per second.
|
Data Source
The data source for the metrics in this category include the following:
|
This metric provides the percentage of the metadata misses per second.
|
Data Source
The data source for the metrics in this category include the following:
|
This metric provides the number of prefetch data misses per second.
|
Data Source
The data source for the metrics in this category include the following:
|
This metric provides the percentage of prefetch data misses.
|
Data Source
The data source for the metrics in this category include the following:
|
This metric provides the number of reads per second.
|
Data Source
The data source for the metrics in this category include the following:
|
The Zombie Processes metric category monitors the orphaned processes in the different variations of UNIX systems.
This metric represents the percentage of all processes running on the system that are currently in zombie state.
|
Data Source
The data sources for this metric include the following:
|
User Action
None.