Use this page to add, edit, or remove monitored objects for multiple threshold metrics. On this page, you can:
Add monitored objects so that they can be monitored at their own thresholds.
Edit Advanced Settings for monitored objects.
Remove monitored objects.
Specify removal of SQL User-Defined Metrics from template destination targets.
Prioritize monitored objects for Management Agent-Alert condition evaluation.
If you want to specify multiple monitored objects with a standardized naming convention, you can use a wildcard character "%" in the object name field ("/" is used to terminate a wildcard pattern) to add multiple objects rather than adding individual monitored objects. For example, if you want to specify tablespaces named USER1, USER2, USER3, then you can specify them collectively as USER%.
Important: You can only use the wildcard character for targets being monitored by Version 10.2 or greater Management Agents.
Changes that you have made on this page are not automatically uploaded to the Management Repository and therefore are not permanent. To make these changes permanent, click Continue to return to the Metric Thresholds page. Your changes will be reflected in the metrics table. Click OK to upload these changes to the Management Repository.
When monitoring multiple objects, you can specify the order in which the Management Agent evaluates the alert conditions. Click Reorder to prioritize the alert evaluation order by monitored object. The Agent does the evaluation from top to bottom--starting with the objects and thresholds specified in the first row in the table, followed by objects in the next row in the table, continuing until the objects in the last row of the table are reached.
If you want to remove two-column SQL user-defined metrics that have already been applied to destination targets, check Mark for Deletion (only available for two-column SQL user-defined metrics). When the template is applied to these targets, the user-defined metric will be removed. However, the user-defined metric will not be removed if the Prevent metric settings on this page from being changed when a monitoring template is applied to the target option has been set for any of the SQL user-defined metric keys.
A user-defined metric that is marked for deletion will be deleted when the template is applied to the target(s) only if the following criteria is met:
A user-defined metric with the same name exists on both the destination target and template.
The return type (String, Numeric) of the user-defined metric is the same on both the destination target and template.
The metric type (Host/SQL user-defined metric, Single Cell/Two-column user-defined metric) is the same on both the destination target and the template.
Examples: Calculating Thresholds
Enterprise Manager Information Roadmap
Copyright © 1996, 2009, Oracle. All rights reserved.