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¶
It is recommended to activate the TrueWatch integration - extension - DataFlux Func (Automata): all preconditions are automatically installed, please proceed with the script installation.
If you need to deploy Func manually, refer to Manual Deployment of Func
Install Script¶
Note: Please prepare the required Amazon AK in advance (for simplicity, you can directly grant the global read-only permission
ReadOnlyAccess
)
Managed Version Activation Script¶
- Log in to the TrueWatch console
- Click on the 【Integration】 menu and select 【Cloud Account Management】
- Click on 【Add Cloud Account】, select 【AWS】, and fill in the required information on the interface. If you have previously configured the cloud account information, you can skip this step.
- Click on 【Test】, and after the test is successful, click on 【Save】. If the test fails, please check if the relevant configuration information is correct and retest.
- Click on 【Cloud Account Management】, and you can see the added cloud account in the list. Click on the corresponding cloud account to enter the details page.
- Click on the 【Integration】 button on the cloud account details page, and find
AWS DMS
under theNot Installed
list. Click on the 【Install】 button, and the installation interface will pop up for installation.
Manual Activation Script¶
-
Log in to the Func console, click on 【Script Market】, enter the TrueWatch script market, and search for
integration_aws_dms
. -
Click on 【Install】, and enter the corresponding parameters: AWS AK ID, AK Secret, and account name.
-
Click on 【Deploy Startup Script】, the system will automatically create the
Startup
script set and automatically configure the corresponding startup scripts. -
After activation, you can see the corresponding automatic trigger configuration in 「Manage / Automatic Trigger Configuration」. Click on 【Execute】 to immediately execute it once without waiting for the scheduled time. Wait for a moment, and you can view the execution task records and corresponding logs.
Verification¶
- In 「Manage / Automatic Trigger Configuration」, confirm whether the corresponding task has the corresponding automatic trigger configuration, and you can also check the corresponding task records and logs to see if there are any exceptions.
- In TrueWatch, check if the asset information exists in 「Infrastructure / Custom」.
- In TrueWatch, check if there is corresponding monitoring data in 「Metrics」.
Metrics¶
After configuring Amazon CloudWatch, the default Measurement is as follows. More Metrics can be collected through configuration Amazon CloudWatch Metrics Details
Instance Metrics¶
The AWS/DMS
namespace includes the following instance Metrics.
Metric | Description |
---|---|
CPUUtilization |
The percentage of allocated vCPU (virtual CPU) currently in use on the instance. Unit: Percentage |
FreeMemory |
The amount of physical memory available for applications, page cache, and the kernel's own data structures. For more information, see the MemFree value in the /proc/memInfo section of the Linux manual page. 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/s |
ReadIOPS |
The average number of disk read I/O operations per second. Unit: Count/s |
WriteThroughput |
The average number of bytes written to disk per second. Unit: Bytes/s |
ReadThroughput |
The average number of bytes read from disk per second. Unit: Bytes/s |
NetworkTransmitThroughput |
The outgoing (transmit) network traffic on the replication instance, including customer database AWS DMS traffic and traffic used for monitoring and replication. Unit: Bytes/s |
NetworkReceiveThroughput |
The incoming (receive) network traffic on the replication instance, including customer database AWS DMS traffic and traffic used for monitoring and replication. Unit: Bytes/s |
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 |
The outgoing data transmitted to the target, in KB per second. CDC ThroughputBandwidth records the outgoing data transmitted at the sampling point. 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 |
The incoming task changes from the source, in rows per second. |
CDCThroughputRowsTarget |
The outgoing task changes to the target, in rows per second. |
Object¶
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 updatesTip 1: The
name
value is the instance ID, used as a unique identifier.