Investigate Alerts

Alerts help keep your Autonomous Database entities up and running by notifying you of issues, so you can take remedial action.

You can proactively review and investigate the alerts for all your Oracle Database entities on the Alerts tile on the Oracle Database Fleet Home page. The Alerts tile displays the total number of new and pre-existing alerts over the last 24 hours and a break down of the alerts based on severity. If you want to view and investigate alerts for a specific entity in your fleet, go to the Database Home page. See Monitor a Specific Autonomous Database.

Alerts are generated either:

• Automatically, for all availability issues, for example, when an Autonomous Database entity is down. No alert rule is required to generate these alerts.

  Note:

  The Unavailable status of an Autonomous Database reflects an unplanned outage, which maps to the Down status in Oracle Management Cloud and an alert is automatically generated. When the Autonomous Database is brought back up and its status changes to Available, the alert is automatically cleared.

  The Stopped status reflects a planned action to stop the Autonomous Database. The status of the Autonomous Database in Oracle Management Cloud is set to Other. An availability alert is also automatically generated to indicate the Autonomous Database is not available for use. When the Autonomous Database is brought back up and its status changes to Available, the alert is automatically cleared.

• Based on custom alert rules that specify a condition, such as the Fixed Threshold condition to generate an alert when a metric exceeds a set metric threshold value. For information on how to create an alert rule and set up alert thresholds and notifications, see Set Up Alert Rules in Using Oracle Infrastructure Monitoring.

To proactively investigate alerts:

1. Go to the Oracle Database Fleet Home page.
2. On the Alerts tile, click the Alerts link.
   The alerts for all your entities are displayed on the Alerts page.
3. Use the Service, Severity, Alert Type, Entity Type, and Search fields to filter and view relevant alerts.

   For example, if you want to view the alerts for your Autonomous Data Warehouse entity, select Monitoring in the Service drop-down list, All in the Severity and Alert Type drop-down lists, and Autonomous Data Warehouse in the Entity Type drop-down list.

   The alerts for the Autonomous Data Warehouse entity are displayed and the information on the Alerts page gives you enough context to start investigating the issues. This information includes:

   • A high-level overview of the total number of alerts and the severity of the alerts. Alert severity is a key component of an alert that translates into the following:
     • Fatal: An entity is down.
     • Critical: A metric has crossed a critical threshold.
     • Warning: A metric has crossed a warning threshold.
   • A detailed description of each alert, which includes:
     • The severity of the alert.
     • The alert message. You can click the alert message for more details such as when the alert was created, updated, and alert history.
     • The entity name and entity type.
     • The date and time when the alert was last updated.
     • The duration of time since the alert was first reported.
4. After you investigate the alert, take the necessary steps to resolve the issue.