This topic describes the monitoring range supported by the task alert feature. This topic also describes how to view the alerts against migration and synchronization tasks created by all users.
Background
OceanBase Migration Service (OMS) monitors events in migration and synchronization tasks, such as the migration task failure, migration task delay, synchronization task failure, inconsistent synchronization task status, and synchronization task delay, and sends alerts to corresponding channels.
Procedure
Log in to the OMS console.
In the left-side navigation pane, choose System Management > Alert Management. The Task Alert Message 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 Task Alert Message page. You can also click the name of the task to which an alert message belongs to go to the page of the corresponding data migration or synchronization task.
The following types of alert events are supported:
Migration task failure: For more information about how to handle this alert, see oms_migration_failed.
Migration task delay: For more information about how to handle this alert, see oms_migration_delay.
Synchronization task failure: For more information about how to handle this alert, see oms_sync_failed.
Inconsistent synchronization task status: For more information about how to handle this alert, see oms_sync_status_inconsistent.
Synchronization task 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 target channel due to network issues or other unknown reasons.
Successful: The alert is sent to the target 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.