Help Center/ Data Replication Service/ Best Practices/ Metrics/ Metric Alarm Configuration Suggestions
Updated on 2025-12-30 GMT+08:00
View PDF
Share

Metric Alarm Configuration Suggestions

Scenarios

You can set alarm rules on the Cloud Eye console to specify the monitored objects and notification policies for your instances and keep track of the instance status. DRS allows you to set threshold rules for instance metrics. If the value of a metric exceeds the threshold, an alarm is triggered. The system automatically sends an alarm notification to the cloud account contact through SMN, helping you learn about the status of your DRS instance in a timely manner.

This section describes how to configure DRS metric alarm rules.

Creating an Alarm Rule

  1. Log in to the management console.
  2. Under Management & Governance of the service list, click Cloud Eye.
  3. In the navigation pane on the left, choose Cloud Service Monitoring > Data Replication Service.
  4. Locate the DB instance for which you want to create an alarm rule and click Create Alarm Rule in the Operation column.
  5. On the Create Alarm Rule page, configure required parameters.

    • Specify Name and Description.
    • Select Use template for Method. The template contains the following common metrics: CPU usage, memory usage, and storage space usage.
    • Click to enable alarm notification. The validity period is 24 hours by default. If the topics you required are not displayed in the drop-down list, click Create an SMN topic. Then, select Generated alarm and Cleared alarm for Trigger Condition.

      Cloud Eye sends notifications only within the validity period specified in the alarm rule.

  6. Click Create. The alarm rule is created.

    For details about how to create alarm rules, see Creating an Alarm Rule in Cloud Eye User Guide.

Table 1 DRS metric alarm configuration suggestions

Metric ID

Metrics Name

Threshold in Best Practices

Alarm Severity in Best Practices

Handling Suggestion

extract_latency

Source Database WAL Extract Lag

Raw data > 600s for three consecutive periods

Major
  • Check the current network status.
  • Check whether the source bandwidth matches the source incremental logs.
  • Check whether there are large transactions on the source database and whether the workloads increase sharply.

apply_latency

Replication Delay

Raw data > 600s for three consecutive periods (configured based on service requirements)

Major
  • Check the CPU usage and response time of the destination database.
  • Check whether slow SQL statements or DDL operations exist in the destination database and whether lock contention occurs.
  • Check whether data on the source database has changed and whether data is imported in batches.

apply_job_status

Task Status

Raw data = 1 for one period

Major

The value 0 indicates the task is normal, 1 indicates the task is abnormal, and 2 indicates the task is suspended. If an alarm is generated, rectify the fault based on the alarm information.

For details about the DRS metrics, see Supported Metrics.

Parent topic: Metrics