All Products
Search
Document Center

Database Autonomy Service:View anomaly alerts

Last Updated:Mar 28, 2026

Anomaly alerts in Database Autonomy Service (DAS) flag suspicious database activity detected by built-in or custom anomaly detection models. Each alert captures what happened, how severe it is, and what action to take. This topic explains how to view and handle anomaly alerts for a single database instance or across all instances at once.

Prerequisites

Before you begin, ensure that you have:

Anomalous event types

Anomalous events fall into three categories:

TypeWhat it detects
Abnormal flowExceptions during data flows — for example, sensitive data downloaded from an unusual geographic location
Abnormal behaviorAbnormal data operations — for example, consecutive invalid password attempts or logons from unusual devices
Custom exceptionsEvents detected by a custom anomaly detection model you have configured

Risk levels

Each alert has a risk level based on the sensitivity level of the matched file.

Event typeRisk levelCondition
Abnormal flowHighHighest sensitivity level of matched file is S3 or above
Abnormal flowMediumHighest sensitivity level of matched file is S1 or S2
Abnormal flowLowHighest sensitivity level of matched file is N/A
Abnormal behaviorMediumHighest sensitivity level of matched file is S2 or above
Abnormal behaviorLowHighest sensitivity level of matched file is S1 or lower
Custom exceptionsConfigured by youDetermined by your model configuration

View alerts for a single database instance

  1. Log on to the DAS console.

  2. In the left-side navigation pane, choose Intelligent O &M Center > Instance Monitoring.

  3. Find the database instance you want to manage and click the instance ID. The instance details page appears.

  4. In the left-side navigation pane, choose Security Center > Security Audit.

  5. On the Security Audit page, click the Alert tab.

  6. Click the Abnormal flow, Abnormal behavior, or Custom exceptions tab to filter by event type and view the corresponding statistics.

  7. To inspect an event, find it in the list and click View Details in the Actions column. The Anomalous Event Details panel shows the basic information, object information, description, and handling history of the event.

  8. To handle an event, click Process in the Actions column. In the Risk Alert panel, configure the following:

    • Anomalous Event Verification — Choose one option:

      • Confirmed and Processed: Select this if the event is a real threat. Locate the affected database instance using the event details and manually handle the anomalous event in the corresponding cloud service. If you select this option without completing remediation, DAS continues generating alerts for the event.

      • Add to Whitelist: Select this if you verify that the detected event is related to a normal operation. DAS stops generating alerts for this event and removes it from the anomalous event list.

    • Add Processing Record: Enter remarks on how you handled the event, for future reference.

  9. To export the alert list, click Export above the anomalous event list.

View alerts for multiple database instances

If security audit is enabled on multiple database instances, their anomaly alerts are consolidated on a single page.

  1. Log on to the DAS console.

  2. In the left-side navigation pane, choose Security Center > Security Audit.

  3. On the Security Audit page, click the Alert tab.

  4. Click the Abnormal flow, Abnormal behavior, or Custom exceptions tab to filter by event type and view the corresponding statistics.

  5. To inspect an event, find it in the list and click View Details in the Actions column. The Anomalous Event Details panel shows the basic information, object information, description, and handling history of the event.

  6. To handle an event, click Process in the Actions column. In the Risk Alert panel, configure the following:

    • Anomalous Event Verification — Choose one option:

      • Confirmed and Processed: Select this if the event is a real threat. Locate the affected database instance using the event details and manually handle the anomalous event in the corresponding cloud service. If you select this option without completing remediation, DAS continues generating alerts for the event.

      • Add to Whitelist: Select this if you verify that the detected event is related to a normal operation. DAS stops generating alerts for this event and removes it from the anomalous event list.

    • Add Processing Record: Enter remarks on how you handled the event, for future reference.

  7. To export the alert list, click Export above the anomalous event list.

What's next

By default, DAS enables all built-in anomaly detection models. You can disable the models that you do not need. To create custom models for specific databases, tables, fields, access sources, or instances, see Configure alert rules.