AWS DMS¶

The displayed Metrics of AWS DMS include data migration speed, latency, data consistency, and migration success rate, which reflect the performance and reliability of DMS during database migration and replication.

Configuration¶

Install Func¶

We recommend enabling Guance Integrations - Extensions - Hosted Func: all prerequisites are installed automatically. Continue with script installation.

To deploy Func yourself, see Self-hosted Func.

Install Script¶

Note: Please prepare the required Amazon AK in advance (for simplicity, you can grant global read-only permissions ReadOnlyAccess)

Activate Script in DataFlux Func (Automata)¶

1. Log in to the Guance console
2. Click the 【Integration】 menu and select 【Cloud Account Management】
3. Click 【Add Cloud Account】, select 【AWS】, and fill in the required information on the interface. If you have already configured the cloud account information before, ignore this step
4. Click 【Test】, and if the test is successful, click 【Save】. If the test fails, please check if the relevant configuration information is correct and test again
5. Click 【Cloud Account Management】, and you can see the added cloud account in the list. Click the corresponding cloud account to enter the details page
6. Click on the 【Integration】 button on the cloud account details page, and find AWS DMS under the Not Installed list. Click on the 【Install】 button, and the installation interface will pop up for installation.

Activate Script Manually¶

1. Log in to the Func console, click on 【Script Market】, enter the Guance script market, and search for integration_aws_dms.

2. Click 【Install】, then enter the corresponding parameters: AWS AK ID, AK Secret, and account name.

3. Click 【Deploy Startup Script】, the system will automatically create the Startup script set and automatically configure the corresponding startup script.

4. After activation, you can see the corresponding automatic trigger configuration in 「Manage / Automatic Trigger Configuration」. Click 【Execute】 to execute it immediately without waiting for the scheduled time. After a while, you can view the execution task records and corresponding logs.

Verification¶

1. Under [Management / Automatic Trigger Configuration], confirm that an automatic trigger configuration exists for the task, and check the task records and logs for errors.
2. In Guance, check [Infrastructure / Custom] for asset information.
3. In Guance, check [Metrics] for the corresponding monitoring data.

Metrics¶

After configuring Amazon CloudWatch, the default Measurement is as follows. More Metrics can be collected through configuration Amazon CloudWatch Metrics Details

Instance Metrics¶

Instance metrics in the AWS/DMS namespace use the ReplicationInstanceIdentifier dimension. SwapUsage supports both instance and task statistics, distinguished by dimensions. With only the instance dimension, it represents swap usage for the entire replication instance.

Task Metrics¶

The following task metrics use both ReplicationInstanceIdentifier and ReplicationTaskIdentifier. With these two dimensions, SwapUsage represents task swap usage in bytes. CDC* metrics apply to ongoing replication, and FullLoad* metrics to full loading. Data availability depends on the task type, phase, and actual workload; null or zero values do not necessarily indicate a collection error.

Objects¶

The collected AWS DMS object data structure can be seen in 「Infrastructure - Custom」

{
  "measurement": "aws_dms",
  "tags": {
    "AvailabilityZone"              :"cn-northwest-1b",
    "class"                         :"aws_dms",
    "cloud_provider"                :"aws",
    "KmsKeyId:arn"                  :"aws-cn:kms:cn-northwest-1:294654068288:key/531cd79a-5a86-47d6-b216-0d63e2e32b3a",
    "name"                          :"hn-test",
    "ReplicationInstanceClass"      :"dms.t3.micro",
    "ReplicationInstanceIdentifier" :"hn-test"
  }
}

Note: The fields in tags may change with subsequent updates

Tip 1: The name value is the instance ID, used as a unique identifier.