Set Up Alarm Definitions for HeatWave DB Systems
You can set up alarm definitions to simplify the process of creating and managing alarms for HeatWave DB systems 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 metrics such as CPU and disk space 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 DB systems. This process notifies you of health and performance issues and serves as a proactive monitoring mechanism to ensure that the DB system operates efficiently and securely. 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 DB system. 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 DB systems: You can clone previously created alarms and apply them to specific DB systems or all the DB systems in a compartment, thereby ensuring standardized monitoring settings.
To go to the Alarm definitions section, go to the MySQL 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 DB system.
- View the alarms created for the DB system or all the DB systems 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
(resource group:mysql_database
) andoci_mysql_database
namespaces. - The
resourceID
dimension is specified when creating alarms for a DB system. The alarms created for all the DB systems in a compartment do not require dimensions to be specified.
For information on:
- The metrics emitted by Database Management in
the
oracle_oci_database
namespace (resource group:mysql_database
), see Database Management Metrics for MySQL HeatWave. - The metrics emitted by the HeatWave service in the
oci_mysql_database
namespace, see HeatWave Service Metrics.
- 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 common operational scenarios for your DB systems.
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 DB system. If duplicate alarms are displayed for a DB system, 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 DB systems in a compartment or the alarms specified for the DB system. 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 DB system. 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 HeatWave DB Systems
Here's the list of the Oracle-recommended alarms available for HeatWave DB systems.
The Monitoring stopped - Metric collection issue Oracle-recommended alarm uses the
MonitoringStatus
metric in the oracle_oci_database
namespace (resource group: mysql_database
) and the remaining
Oracle-recommended alarms for HeatWave DB systems use metrics in the
oci_mysql_database
namespace.
Oracle-recommended Alarm | Severity | Description |
---|---|---|
CPU utilization (%) | Critical | Alarm created using the CPUUtilization
metric to notify when the CPU utilization for the DB system host or
HeatWave nodes exceeds the specified threshold.
By
default, this alarm is fired when the mean of the
Default alarm query:
|
CPU utilization (%) | Warning | Alarm created using the CPUUtilization
metric to notify when the CPU utilization for the DB system host or
HeatWave nodes exceeds the specified threshold.
By
default, this alarm is fired when the mean of the
Default alarm query:
|
Disk space utilization (%) | Critical | Alarm created using the
DbVolumeUtilization metric to notify when the total
space utilization of the DB system volumes exceeds the specified
threshold.
By default, this alarm is fired when the
mean of the Default alarm
query: |
Disk space utilization (%) | Warning | Alarm created using the
DbVolumeUtilization metric to notify when the total
space utilization of the DB system volumes exceeds the specified
threshold.
By default, this alarm is fired when the
mean of the Default alarm
query: |
Disk write bytes | Critical | Alarm created using the
DbVolumeWriteBytes metric to notify when the total
bytes written to the DB system volumes is equal to 0.
By
default, this alarm is fired when the mean of the
Default alarm query:
|
HeatWave health status | Critical | Alarm created using the HeatWaveHealth
metric to notify when the HeatWave cluster health status is not healthy,
and exceeds the specified threshold.
By default, this
alarm is fired when the mean of the Default alarm query:
|
Memory utilization (%) | Critical | Alarm created using the
MemoryUtilization metric to notify when the memory
utilization for the DB system host or HeatWave nodes exceeds the
specified threshold.
By default, this alarm is fired when
the mean of the Default alarm
query: |
Memory utilization (%) | Warning | Alarm created using the
MemoryUtilization metric to notify when the memory
utilization for the DB system host or HeatWave nodes 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
MonitoringStatus metric to notify when the DB
system 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 DB system 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. |
Network receive bytes | Critical | Alarm created using the
NetworkReceiveBytes metric to notify when the total
network receive bytes for the DB system is equal to 0.
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 DB systems or all the DB systems in a compartment.
To clone alarms:
When cloning alarms, you may create duplicate alarms. If duplicate alarms are listed for the DB systems, 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.