The System Monitoring Plug-in Metric Reference Manual for Virtualization Management lists all the plug-ins metrics for database management that Enterprise Manager monitors. This manual shows all the metric help available online, eliminating the need to have the Grid Control Console up and running.
This preface describes:
This manual contains a chapter for the VMWare ESX Server. The metrics in this chapters appears in alphabetical order according to category.
The information for each metric comprises a description and user action if available:
Provides an explanation following the metric name. This text defines the metric and, when available, provides additional information pertinent to the metric.
Suggests how to solve the problem causing the alert.
The Metric Summary table in Enterprise Manager Grid Control is part of the overall metric information. The following table provides descriptions of columns in the Enterprise Manager Metric Summary table.
|Column Header||Column Definition|
|Target Version||Version of the target, for example, 9.0.2.x and 10.1.0.x. The x at the end of a version (for example, 9.0.2.x) represents the subsequent patchsets associated with that release.|
|Server Evaluation Frequency||The rate at which the metric is evaluated to determine whether it has crossed its threshold. For server-generated alerts, the evaluation frequency is determined by Oracle Database internals. For example, if the evaluation frequency is 10 minutes, when the Average File Write Time degrades to the point an alert should trigger, it could be almost 10 minutes before Enterprise Manager receives an indication of the alert. This column is present in the Metric Collection Summary table only for Oracle Database 10g metrics.|
|Collection Schedule||The rate at which the Management Agent collects data. The collection frequency for a metric comes from the Enterprise Manager default collection file for that target type.|
|Upload Interval||The rate at which the Management Agent moves data to the Management Repository. For example, upload every nth collection. The upload frequency for a metric comes from the Enterprise Manager default collection file for that target type. This column is present in the Metric Collection Summary table only when the Upload Frequency is different from the Collection Frequency.|
|Comparison Operator||The comparison method Enterprise Manager uses to evaluate the metric value against the threshold values.|
|Default Warning Threshold||Value that indicates whether a warning alert should be initiated. If the evaluation of the warning threshold value returns a result of TRUE for the specified number of consecutive occurrences defined for the metric, an alert triggers at the warning severity level.|
|Default Critical Threshold||Value that indicates whether a critical alert should be initiated. If the evaluation of the critical threshold value returns a result of TRUE for the specified number of consecutive occurrences defined for the metric, an alert triggers at the critical severity level.|
|Consecutive Number of Occurrences Preceding Notification||Consecutive number of times a metric's value reaches either the warning threshold or critical threshold before a notification is sent.|
|Alert Text||Message indicating why the alert was generated. Words that display between percent signs (%) denote variables. For example,
To reduce the page count in this document, the following abbreviations and acronyms are used:
|Agent||Oracle Management Agent|
|OMS||Oracle Management Service|
|Repository||Oracle Management Repository|
A metric is a unit of measurement used to determine the health of a target. It is through the use of metrics and associated thresholds that Enterprise Manager sends out alerts notifying you of problems with the target.
Thresholds are boundary values against which monitored metric values are compared. For example, for each disk device associated with the Disk Utilization (%) metric, you can define a different warning and critical threshold. Some of the thresholds are predefined by Oracle; others are not.
After a threshold is reached, an alert is generated. An alert is an indicator signifying that a particular condition has been encountered and is triggered when one of the following conditions is true:
A threshold is reached.
An alert has been cleared.
The availability of a monitored service changes. For example, the availability of an application server changes from up to down.
A specific condition occurs. For example, an alert is triggered whenever an error message is written to a database alert log file.
Alerts are detected through a polling-based mechanism by checking for the monitored condition from a separate process at regular, predefined intervals.
See Also:See the Oracle Enterprise Manager Concepts manual and the Enterprise Manager online help for additional information about metrics, thresholds, and alerts
Out of the box, Enterprise Manager comes with thresholds for critical metrics. Warning and critical thresholds are used to generate an alert, letting you know of impending problems so that you can address them in a timely manner.
To better suit the monitoring needs of your organization, you can edit the thresholds provided by Enterprise Manager and define new thresholds. When defining thresholds, the key is to choose acceptable values to avoid unnecessary alerts, while still being notified of issues in a timely manner.
You can establish thresholds that will provide pertinent information in a timely manner by defining metric baselines that reflect how your system runs for a normal period of time.
The metrics listed on the Edit Thresholds page are either default metrics provided by Oracle or metrics whose thresholds you can change.
The Specifying Multiple Thresholds functionality allows you to define various subsets of data that can have different thresholds. By specifying multiple thresholds, you can refine the data used to trigger alerts, which is one of the key benefits of using Enterprise Manager.The key in specifying multiple thresholds is to determine how the comparison relates to the metric threshold as a whole. What benefit will be realized by defining a more stringent or lax threshold for that particular device, mount point, and so on?For example, using the Average Disk I/O Service Time metric, you can define warning and critical thresholds to be applied to all disks (sd0 and sd1), or you can define different warning and critical thresholds for a specific disk (sd0). This allows you to adjust the thresholds for sd0 to be more stringent or lax for that particular disk.
To access metrics in the Grid Control Console, use the All Metrics page associated with a particular target by doing the following:
From the Grid Control Console, choose the target.
On the target's home page, click All Metrics in the Related Links section.
On the All Metrics page, choose the metric of interest and click Help. The help for that metric appears.