Set Up Alarm Definitions
You can set up alarm definitions to simplify the process of creating and managing alarms in Database Management.
In the Alarm definitions section, you can use the available standardized set of rules and thresholds and create Oracle-recommended alarms to proactively monitor important database metrics such as CPU and storage utilization. Oracle-recommended alarms in Database Management greatly simplify the process of creating an Oracle Cloud Infrastructure Monitoring service alarm and setting up a notification system for common operational scenarios for your Managed Databases. This process notifies you of database health and performance issues and serves as a proactive monitoring mechanism to ensure that the Managed Database operates efficiently, securely, and in alignment with Oracle Database monitoring best practices. In addition, if you want to use the complete set of options available when creating alarms, you have the option of navigating to the Monitoring service and creating custom alarms for the Managed Database. Here are a few other benefits of the Alarm definitions feature:
- Edit and customize alarms: You can edit the preconfigured values for Oracle-recommended alarms and the values for custom alarms to customize them. This provides you with the flexibility to edit an alarm to meet specific requirements.
- Clone alarms for multiple databases: You can clone previously created alarms and apply them to specific Managed Databases or all the Managed Databases in a compartment, thereby ensuring standardized monitoring settings.
To go to the Alarm definitions section, go to the Managed database details page and click Alarm definitions on the left pane under Resources.
In the Alarm definitions section, you can:
- Create Oracle-recommended alarms or navigate to the Monitoring service to create custom alarms for a Managed Database.
- View the alarms created for the Managed Database or all the Managed
Databases in the compartment.
Note
To view alarms in the Alarm definitions section, you must ensure that:- The alarms are created using the Oracle Cloud Infrastructure (out-of-the-box) metrics emitted in the
oracle_oci_database
namespace for External Databases and Oracle Cloud Databases and theoci_autonomous_database
namespace for Autonomous Databases. For External Databases, if you've created alarms on metric extensions (oracle_metric_extensions_appmgmt
namespace), then you can view those alarms too. The Alarm definitions feature is not supported for the metrics emitted in theoci_database_cluster
andoci_database
namespaces. - The
resourceID
dimension is specified when creating alarms for a database. The alarms created for all the databases in a compartment do not require dimensions to be specified.
For information on the namespaces and dimensions of the Oracle Databases monitored and managed by Database Management, see Database Management Metrics for Oracle Databases.
- The alarms are created using the Oracle Cloud Infrastructure (out-of-the-box) metrics emitted in the
- Edit alarms
- Clone alarms
- Delete alarms
In addition to Database Management permissions, other Oracle Cloud Infrastructure service permissions are required to perform alarm-related tasks. For information on:
- Monitoring service permissions required to create alarms, see Managing Alarms.
- Oracle Cloud Infrastructure Notification service permissions required to create and use topics, see Managing Topics.
Create Recommended Alarms
You can create Oracle-recommended alarms that are preconfigured for the most common database operational scenarios.
Once the alarms are created, you can:
- Click the alarm to view the alarm details on the Alarm
Definitions page in the Monitoring service. For
Oracle-recommended alarms, the provider: DBM free-form
tag is added by default during the creation process and is displayed in the
Tags section.
Note
It's possible that different users create the same Oracle-recommended alarm for a Managed Database. If duplicate alarms are displayed for a database, click the alarm to view information such as who created the alarm and when it was created in the Tags section on the Alarm Definitions page in the Monitoring service. - Use the Search field and the filter
drop-down lists above the list of alarms to filter the alarms:
- Severity filter: Select an alarm severity option to only view the alarms of a particular severity type.
- Scope filter: Select one of the available options to view the alarms specified for all the Managed Databases in a compartment or the alarms specified for the Managed Database. By default, all the alarms are displayed.
- Origin filter: Select one of the available options to view the Oracle-recommended alarms or the custom alarms created in the Monitoring service, for the Managed Database. By default, all the alarms are displayed.
- Click the Actions icon () and click Edit threshold to edit the basic alarm values in Database Management or click Edit alarm to view and edit the complete set of values specified for the alarm in the Monitoring service. For information, see Edit Alarms.
- Select alarms and click Clone to clone the alarms. For information, see Clone Alarms.
- Select alarms and click Delete to delete the alarms.
Oracle-recommended Alarms for Managed Databases
Here's the list of the Oracle-recommended alarms available for Managed Databases.
Oracle-recommended alarms for External Databases and Oracle Cloud Databases
The Oracle-recommended alarms for External Databases and Oracle Cloud Databases are
created using the metrics in the oracle_oci_database
namespace.
Oracle-recommended Alarm | Severity | Description |
---|---|---|
Blocking sessions count | Critical | Alarm created using the
BlockingSessions metric to notify when the
number of blocking sessions exceeds the specified threshold.
By default, this alarm is fired when the mean of
the Default alarm query:
Note that this alarm is not available for CDBs. |
CPU utilization (%) | Critical | Alarm created using the
CpuUtilization metric to notify when the CPU
utilization for the database exceeds the specified threshold.
By default, this alarm is fired when the mean of
the Default alarm query:
|
Flash recovery area utilization (%) | Critical | Alarm created using the
FRAUtilization metric to notify when the flash
recovery area utilization for the database exceeds the specified
threshold.
By default, this alarm is fired when
the mean of the Default alarm query: Note that this alarm is not available for PDBs. |
Monitoring stopped - Metric collection issue | Critical | Alarm created using the
MonitoringStatus metric to notify when the
database is down. This alarm is fired when the metric collection has
stopped due to issues related to network, agent, credentials,
connection, or missing data or when the database is down.
This is an advanced alarm and cannot be edited in Database Management. You can edit this alarm in the Oracle Cloud Infrastructure Monitoring service, however, it's recommended that you do not edit it. |
Processes utilization (%) | Critical | Alarm created using the
ProcessLimitUtilization metric to notify when
the process limit utilization for the database exceeds the specified
threshold.
By default, this alarm is fired when
the mean of the Default alarm query: |
Storage utilization (%) | Warning | Alarm created using the
StorageUtilization metric to notify when the
allocated space for all the tablespaces in the database exceeds the
specified threshold.
By default, this alarm is fired
when the mean of the Default alarm query: |
Storage utilization (%) | Critical | Alarm created using the
StorageUtilization metric to notify when the
allocated space for all the tablespaces in the database exceeds the
specified threshold.
By default, this alarm is fired
when the mean of the Default alarm query: |
Tablespace space utilization (%) | Warning | Alarm created using the
StorageUtilizationByTablespace metric to notify
when the space used by a tablespace exceeds the specified threshold.
For CDBs, the alarm is fired when the space used by the root
container tablespace exceeds the specified threshold.
By default, this alarm is fired when the mean of the
Default alarm query:
|
Tablespace space utilization (%) | Critical | Alarm created using the
StorageUtilizationByTablespace metric to notify
when the space used by a tablespace exceeds the specified threshold.
For CDBs, the alarm is fired when the space used by the root
container tablespace exceeds the specified threshold.
By default, this alarm is fired when the mean of the
Default alarm query:
|
Oracle-recommended alarms for Autonomous Databases
The Oracle-recommended alarms for Autonomous Databases are created using the metrics
in the oci_autonomous_database
namespace.
Oracle-recommended Alarm | Severity | Description |
---|---|---|
CPU utilization (%) | Critical | Alarm created using the
CpuUtilization metric to notify when the CPU
utilization for the database exceeds the specified threshold.
By default, this alarm is fired when the mean of
the Default alarm query:
|
Failed logins | Warning | Alarm created using the FailedLogons
metric to notify when the number of failed logins exceeds the
specified threshold.
By default, this alarm is fired
when the mean of the Default alarm query: |
Failed logins | Critical | Alarm created using the FailedLogons
metric to notify when the number of failed logins exceeds the
specified threshold.
By default, this alarm is fired
when the mean of the Default alarm query: |
Monitoring stopped - Metric collection issue | Critical | Alarm created using the
DatabaseAvailability metric to notify when the
database is down. This alarm is fired when the metric collection has
stopped due to issues related to network, agent, credentials,
connection, or missing data or when the database is down.
This is an advanced alarm and cannot be edited in Database Management. You can edit this alarm in the Monitoring service, however, it's recommended that you do not edit it. Note that this alarm is not available for Autonomous Databases on Dedicated Exadata Infrastructure. |
Sessions | Warning | Alarm created using the Sessions
metric to notify when the number of sessions exceeds the specified
threshold.
By default, this alarm is fired when
the mean of the Default alarm
query: |
Storage utilization (%) | Warning | Alarm created using the
StorageUtilization metric to notify when the
allocated space for all the tablespaces in the database exceeds the
specified threshold.
By default, this alarm is fired
when the mean of the Default alarm query: |
Storage utilization (%) | Critical | Alarm created using the
StorageUtilization metric to notify when the
allocated space for all the tablespaces in the database exceeds the
specified threshold.
By default, this alarm is fired
when the mean of the Default alarm query: |
Edit Alarms
You can edit the values specified for an alarm to customize the alarm to meet your requirements.
The editing capability in the Alarm definitions section provides you with the flexibility to make changes to alarm values and customize the alarm. In this section, you can:
- Click Edit threshold when creating an Oracle-recommended alarm or for a previously created Oracle-recommended or custom alarm to edit basic alarm values such as threshold, interval, and severity. For Oracle-recommended alarms, this enables you to make changes to the preconfigured values to meet specific requirements.
- Click Edit alarm for a previously created Oracle-recommended or custom alarm to view and edit the complete set of values specified for the alarm in the Oracle Cloud Infrastructure Monitoring service.
To edit basic alarm values for Oracle-recommended or custom alarms in Database Management:
Clone Alarms
You can clone existing Oracle-recommended or custom alarms and apply them to specific Managed Databases or all the Managed Databases in a compartment.
To clone alarms:
When cloning alarms, you may create duplicate alarms. If duplicate alarms are listed for the Managed Database, click the alarm to view information such as who created the alarm and when it was created in the Tags section on the Alarm Definitions page in the Oracle Cloud Infrastructure Monitoring service.