Skip to content

AWS DMS

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

Configuration

Install Func

It is recommended to enable Guance integration - extension - hosted Func: all prerequisites are automatically installed. Please continue with the script installation.

If you deploy Func yourself, refer to Self-hosted Func

Installation Script

Note: Prepare an Amazon AK that meets the requirements in advance (for simplicity, you can directly grant global read-only permission ReadOnlyAccess).

Hosted Edition Activation Script

  1. Log in to the Guance console.
  2. Click on the 【Integration】 menu and select 【Cloud Account Management】.
  3. Click 【Add Cloud Account】, choose 【AWS】, and fill in the required information. If you have already configured cloud account information, skip this step.
  4. Click 【Test】, and after a successful test, click 【Save】. If the test fails, check whether the related configuration information is correct and retest.
  5. In the 【Cloud Account Management】 list, you can see the added cloud account. Click on the corresponding cloud account to enter the details page.
  6. Click the 【Integration】 button on the cloud account details page. Under the Not Installed list, find AWS DMS, click the 【Install】 button, and follow the installation interface to complete the installation.

Manual Activation Script

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

  2. After clicking 【Install】, input the corresponding parameters: AWS AK ID, AK Secret, and account name.

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

  4. After enabling, you can see the corresponding automatic trigger configuration under 「Management / Automatic Trigger Configuration」. Click 【Execute】 to run it immediately without waiting for the scheduled time. Wait a moment, and you can view the execution task records and corresponding logs.

We default collect some configurations; see the Metrics section for more details.

Verification

  1. Confirm in 「Management / Automatic Trigger Configuration」 whether the corresponding tasks have the corresponding automatic trigger configuration, and check the task records and logs for any anomalies.
  2. In Guance, 「Infrastructure / Custom」, check if there is asset information.
  3. In Guance, 「Metrics」, check if there are corresponding monitoring data.

Metrics

After configuring Amazon - Cloud Monitoring, the default Measurement set is as follows. You can collect more Metrics through configuration. Amazon Cloud Monitoring Metrics Details

Instance Metrics

The AWS/DMS namespace includes the following instance Metrics.

Metric Description
CPUUtilization The percentage of allocated vCPUs (virtual CPUs) currently in use on the instance. Unit: Percentage
FreeMemory The amount of physical memory available for applications, page cache, and kernel data structures. For more information, see the MemFree value in the Linux manual /proc/memInfo section. Unit: Bytes
FreeStorageSpace The size of available storage space. Unit: Bytes
WriteIOPS The average number of disk write I/O operations per second. Unit: Count/Second
ReadIOPS The average number of disk read I/O operations per second. Unit: Count/Second
WriteThroughput The average number of bytes written to the disk per second. Unit: Bytes/Second
ReadThroughput The average number of bytes read from the disk per second. Unit: Bytes/Second
NetworkTransmitThroughput Outbound (transmit) network traffic on the replication instance, including customer database AWS DMS traffic and traffic used for monitoring and replication. Unit: Bytes/Second
NetworkReceiveThroughput Inbound (receive) network traffic on the replication instance, including customer database AWS DMS traffic and traffic used for monitoring and replication. Unit: Bytes/Second
CDCChangesMemorySource The number of rows accumulated in memory and waiting to be committed from the source. You can view this metric together with CDC ChangesDiskSource.
CDCChangesMemoryTarget The number of rows accumulated in memory and waiting to be committed to the target. You can view this metric together with CDC ChangesDiskTarget.
CDCChangesDiskSource The number of rows accumulated on disk and waiting to be committed from the source. You can view this metric together with CDC ChangesMemorySource.
CDCChangesDiskTarget The number of rows accumulated on disk and waiting to be committed to the target. You can view this metric together with CDC ChangesMemoryTarget.
CDCThroughputBandwidthTarget Outbound data transmitted to the target, in KB per second. CDC ThroughputBandwidth records outbound data transmitted at sampling points. If no task network traffic is found, this value is zero. Since CDC does not publish long-running transactions, network traffic may not be recorded.
CDCThroughputRowsSource Incoming task changes for the source, in rows per second.
CDCThroughputRowsTarget Outgoing task changes for the target, in rows per second.

Objects

Collected AWS DMS object data structure can be viewed under 「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: Fields in tags may change with subsequent updates.

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

Feedback

Is this page helpful? ×