Makinge use of Standard and Customized templates

Create standard monitoring templates for each of your target types to be monitored. If for a specific target customization is needed, don’t be tempted to change target’s thresholds but use Customized templates instead.

Using this approach, you are alway able to reconstruct the monitoring setup for a specific target by applying the standard template and then applying it’s customized template.

Create metrics design

When setting up target monitoring,start with designing you metrics and metric thresholds for each of your target types.

You might want to do this by simply creating a spreadsheet to identify for what target types you would like to test which metrics and to use what thresholds.

Changing tablespace metrics in monitoring template

While applying new monitoring templates to a database instance target, we encountered the following:

When changing thresholds for ‘Tablespace Space Used’ metrics, both Warning and Critical threshold must be defined. Omitting one of these will result in no changes at the target. Applying the template to the target seems to function successfully (no errors shown), however no changes will be made to the target. This is because of the fact that database package DBMS_SERVER_ALERT doesn’t allow you to omit one of the thresholds (warning or critical) and will give an error message.

Configuration of Metrics in Oracle Enterprise Manager

Monitoring targets using OEM heavily leans on Metrics and Policies. As you must have noticed, after installation of Oracle Enterprise Manager Hundreds of metrics and polices are installed. These metrics and policies will most probably start generating tons of alerts and at the end of the day you might end up with an EM console indicating many target alerts and policy violations.

Configuration of Metrics and Policies in Oracle Enterprise Manager