This topic describes the monitoring range supported by the project alert feature. This topic also describes how to view the alerts against migration and synchronization projects created by all users.
Background
OceanBase Migration Service (OMS) monitors events in migration and synchronization projects, such as the migration project failure, migration project delay, synchronization project failure, inconsistent synchronization project status, and synchronization project delay, and sends alerts to corresponding channels.
Procedure
Log on to the OMS console.
In the left-side navigation pane, choose System Management > Alerts. The Project Alert Information page appears.
By default, this page displays alerts of the last 7 days. In the upper-right corner of the page, you can select Last 7 Days, Last 3 Weeks, Last Month, or Last 3 Months from the drop-down list to view alerts within different ranges of time. You can also enter the alert ID or message content in the search box in the upper-right corner to search for an alert.
You can filter alerts by using the Alert Events and Sending Status columns on the Project Alert Information page. You can also click the name of the project to which an alert message belongs to go to the page of the corresponding data migration or synchronization project.
The following types of alert events are supported:
Migration project failure: For more information about how to handle this alert, see oms_migration_failed.
Migration project delay: For more information about how to handle this alert, see oms_migration_delay.
Synchronization project failure: For more information about how to handle this alert, see oms_sync_failed.
Inconsistent synchronization project status: For more information about how to handle this alert, see oms_sync_status_inconsistent.
Synchronization project delay: For more information about how to handle this alert, see oms_sync_delay.
An alert can be found in one of the following states:
Pending: The alert is waiting for its sending to be scheduled.
Failed: The alert failed to be sent to the destination channel due to network issues or other unknown reasons.
Successful: The alert is sent to the destination channel, such as OceanBase Cloud Platform (OCP).
Completed: If the alert is not triggered within 3 hours, the alert status becomes Completed.
Sent again: The alert is sent again because the last sending failed.