Amazon Database Migration Service
Dynatrace ingests metrics for multiple preselected namespaces, including Amazon Database Migration Service. You can view metrics for each service instance, split metrics into multiple dimensions, and create custom charts that you can pin to your dashboards.
Prerequisites
To enable monitoring for this service, you need
- An Environment or Cluster ActiveGate version 1.197+
- Dynatrace version 1.200+
- An updated AWS monitoring policy to include the additional AWS services.
To update the AWS IAM policy, use the JSON below, containing the monitoring policy (permissions) for all supporting services.
If you don't want to add permissions to all services, and just select permissions for certain services, consult the table below. The table contains a set of permissions that are required for all services (All monitored Amazon services) and, for each supporting service, a list of optional permissions specific to that service.
Example of JSON policy for one single service.
In this example, from the complete list of permissions you need to select
"apigateway:GET"
for Amazon API Gateway"cloudwatch:GetMetricData"
,"cloudwatch:GetMetricStatistics"
,"cloudwatch:ListMetrics"
,"sts:GetCallerIdentity"
,"tag:GetResources"
,"tag:GetTagKeys"
, and"ec2:DescribeAvailabilityZones"
for All monitored Amazon services.
Enable monitoring
To enable monitoring for this service, you first need to integrate Dynatrace with Amazon Web Services:
Add the service to monitoring
In order to view the service metrics, you must add the service to monitoring in your Dynatrace environment.
Beginning in early 2021, all cloud services will consume Davis Data Units (DDUs). The amount of DDU consumption per service instance depends on the number of monitored metrics and their dimensions (each metric dimension results in the ingestion of 1 data point; 1 data point consumes 0.001 DDUs). For DDU consumption estimates per service instance (recommended metrics only, predefined dimensions, and assumed dimension values), see DDU consumption estimates for per cloud service instance.
Monitor resources based on tags
You can choose to monitor resources based on existing AWS tags, as Dynatrace automatically imports them from service instances. Nevertheless, the transition from AWS to Dynatrace tagging isn't supported for all AWS services. Expand the table below to see which supporting services are filtered by tagging.
To monitor resources based on tags
- Go to Settings > Cloud and virtualization > AWS and select the AWS instance.
- For Resource monitoring method, select Monitor resources based on tags.
- Enter the Key and Value.
- Select Save.
Configure service metrics
Once you add a service, Dynatrace starts automatically collecting a suite of metrics for this particular service. These are recommended metrics.
Recommended metrics:
- Are enabled by default
- Can't be disabled
- Can have recommended dimensions (enabled by default, can't be disabled)
- Can have optional dimensions (disabled by default, can be enabled)
Apart from the recommended metrics, most services have the possibility of enabling optional metrics.
Optional metrics:
- Can be added and configured manually
View service metrics
Once you add the service to monitoring, you can view the service metrics in your Dynatrace environment either on your dashboard page or on the custom device overview page.
Import preset dashboards
Dynatrace provides preset AWS dashboards that you can import from GitHub to your environment's Dashboards page.
Note: To save a preset dashboard locally, create a new JSON file on your local machine and copy-paste the content of the JSON file from GitHub into the new file.
Once you save a preset dashboard locally, there are two ways to import it.
Available metrics
Name | Description | Unit | Statistics | Dimensions | Recommended |
---|---|---|---|---|---|
CDCChangesDiskSource | Amount of rows accumulating on disk and waiting to be committed from the source | Count | Sum | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | |
CDCChangesDiskTarget | Amount of rows accumulating on disk and waiting to be committed to the target | Count | Sum | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | |
CDCChangesMemorySource | Amount of rows accumulating in memory and waiting to be committed from the source | Count | Sum | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | |
CDCChangesMemoryTarget | Amount of rows accumulating in memory and waiting to be committed to the target | Count | Sum | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | |
CDCIncomingChanges | The total number of change events at a point in time that are waiting to be applied to the target | Count | Sum | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
CDCLatencySource | The gap, in seconds, between the last event captured from the source endpoint and the current system timestamp of the AWS DMS instance. CDCLatencySource represents the latency between source and replication instance. | Seconds | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
CDCLatencyTarget | The gap, in seconds, between the first event timestamp waiting to commit on the target and the current timestamp of the AWS DMS instance. CDCLatencyTarget represents the latency between replication instance and target. | Seconds | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
CDCThroughputBandwidthSource | Incoming data received for the source in KB per second | Kilobytes/Second | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
CDCThroughputBandwidthTarget | Outgoing data transmitted for the target in KB per second | Kilobytes/Second | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
CDCThroughputRowsSource | Incoming task changes from the source in rows per second | Count/Second | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
CDCThroughputRowsTarget | Outgoing task changes for the target in rows per second | Count/Second | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
CPUAllocated | The percentage of CPU maximally allocated for the task (0 means no limit) | Percent | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | |
CPUUtilization | The amount of CPU used | Percent | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
CPUUtilization | Percent | Multi | ReplicationInstanceIdentifier | ✔️ | |
CPUUtilization | Percent | Multi | Region, ReplicationInstanceExternalResourceId | ✔️ | |
CPUUtilization | Percent | Multi | Region | ✔️ | |
CPUUtilization | Percent | Multi | Region, InstanceClass | ||
DiskQueueDepth | The number of outstanding I/Os (read/write requests) waiting to access the disk | Count | Multi | Region, ReplicationInstanceExternalResourceId | |
DiskQueueDepth | Count | Multi | Region | ||
DiskQueueDepth | Count | Multi | Region, InstanceClass | ||
DiskQueueDepth | Count | Multi | ReplicationInstanceIdentifier | ||
FreeStorageSpace | The amount of available storage space | Bytes | Multi | ReplicationInstanceIdentifier | ✔️ |
FreeStorageSpace | Bytes | Multi | Region, ReplicationInstanceExternalResourceId | ||
FreeStorageSpace | Bytes | Multi | Region | ||
FreeStorageSpace | Bytes | Multi | Region, InstanceClass | ||
FreeableMemory | The amount of available RAM | Bytes | Multi | ReplicationInstanceIdentifier | ✔️ |
FreeableMemory | Bytes | Multi | Region, ReplicationInstanceExternalResourceId | ||
FreeableMemory | Bytes | Multi | Region | ||
FreeableMemory | Bytes | Multi | Region, InstanceClass | ||
FullLoadThroughputBandwidthSource | Incoming data received from a full load from the source in kilobytes (KB) per second | Kilobytes/Second | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
FullLoadThroughputBandwidthTarget | Outgoing data transmitted from a full load for the target in kilobytes (KB) per second | Kilobytes/Second | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
FullLoadThroughputRowsSource | Incoming changes from a full load from the source in rows per second | Count/Second | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
FullLoadThroughputRowsTarget | Outgoing changes from a full load for the target in rows per second | Count/Second | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
MemoryAllocated | The maximum allocation of memory for the task (0 means no limits) | Megabytes | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | |
MemoryUsage | The resident set size (RSS) occupied by a task. It indicates the portion of memory occupied by a task held in main memory (RAM). | Megabytes | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
NetworkReceiveThroughput | The incoming (receive) network traffic on the replication instance, including both customer database traffic and AWS DMS traffic used for monitoring and replication | Bytes/Second | Multi | ReplicationInstanceIdentifier | ✔️ |
NetworkReceiveThroughput | Bytes/Second | Multi | Region, ReplicationInstanceExternalResourceId | ||
NetworkReceiveThroughput | Bytes/Second | Multi | Region | ||
NetworkReceiveThroughput | Bytes/Second | Multi | Region, InstanceClass | ||
NetworkTransmitThroughput | The outgoing (transmit) network traffic on the replication instance, including both customer database traffic and AWS DMS traffic used for monitoring and replication | Bytes/Second | Multi | ReplicationInstanceIdentifier | ✔️ |
NetworkTransmitThroughput | Bytes/Second | Multi | Region, ReplicationInstanceExternalResourceId | ||
NetworkTransmitThroughput | Bytes/Second | Multi | Region | ||
NetworkTransmitThroughput | Bytes/Second | Multi | Region, InstanceClass | ||
ReadIOPS | The average number of disk read I/O operations per second | Count/Second | Multi | ReplicationInstanceIdentifier | ✔️ |
ReadIOPS | Count/Second | Multi | Region, ReplicationInstanceExternalResourceId | ||
ReadIOPS | Count/Second | Multi | Region | ||
ReadIOPS | Count/Second | Multi | Region, InstanceClass | ||
ReadLatency | The average amount of time taken per disk I/O (input) operation | Seconds | Multi | ReplicationInstanceIdentifier | ✔️ |
ReadLatency | Seconds | Multi | Region, ReplicationInstanceExternalResourceId | ||
ReadLatency | Seconds | Multi | Region | ||
ReadLatency | Seconds | Multi | Region, InstanceClass | ||
ReadThroughput | The average number of bytes read from disk per second | Bytes/Second | Multi | ReplicationInstanceIdentifier | ✔️ |
ReadThroughput | Bytes/Second | Multi | Region, ReplicationInstanceExternalResourceId | ||
ReadThroughput | Bytes/Second | Multi | Region | ||
ReadThroughput | Bytes/Second | Multi | Region, InstanceClass | ||
RecoveryCount | Count | Sum | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ | |
RunCounter | Count | Sum | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ | |
SwapUsage | The amount of swap space used on the replication instance | Bytes | Multi | ReplicationInstanceIdentifier | ✔️ |
SwapUsage | Bytes | Multi | Region, ReplicationInstanceExternalResourceId | ||
SwapUsage | Bytes | Multi | Region | ||
SwapUsage | Bytes | Multi | Region, InstanceClass | ||
ValidationAttemptedRecordCount | Number of rows that validation was attempted, per minute | Count | Sum | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
ValidationBulkQuerySourceLatency | AWS DMS can do data validation in bulk, especially in certain scenarios during a full-load or ongoing replication when there are many changes. This metric indicates the latency required to read a bulk set of data from the source endpoint. | Milliseconds | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
ValidationBulkQueryTargetLatency | AWS DMS can do data validation in bulk, especially in certain scenarios during a full-load or ongoing replication when there are many changes. This metric indicates the latency required to read a bulk set of data on the target endpoint. | Milliseconds | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
ValidationFailedOverallCount | Number of rows where validation failed | Count | Sum | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
ValidationItemQuerySourceLatency | During ongoing replication, data validation can identify ongoing changes and validate those changes. This metric indicates the latency in reading those changes from the source. | Milliseconds | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | |
ValidationItemQueryTargetLatency | During ongoing replication, data validation can identify ongoing changes and validate the changes row by row. This metric gives us the latency in reading those changes from the target. | Milliseconds | Multi | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | |
ValidationPendingOverallCount | Number of rows where the validation is still pending | Count | Sum | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
ValidationSucceededRecordCount | Number of rows that AWS DMS validated, per minute | Count | Sum | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
ValidationSuspendedOverallCount | Number of rows where validation was suspended | Count | Sum | ReplicationInstanceIdentifier, ReplicationTaskIdentifier | ✔️ |
WriteIOPS | The average number of disk write I/O operations per second | Count/Second | Multi | ReplicationInstanceIdentifier | ✔️ |
WriteIOPS | Count/Second | Multi | Region, ReplicationInstanceExternalResourceId | ||
WriteIOPS | Count/Second | Multi | Region | ||
WriteIOPS | Count/Second | Multi | Region, InstanceClass | ||
WriteLatency | The average amount of time taken per disk I/O (output) operation | Seconds | Multi | ReplicationInstanceIdentifier | ✔️ |
WriteLatency | Seconds | Multi | Region, ReplicationInstanceExternalResourceId | ||
WriteLatency | Seconds | Multi | Region | ||
WriteLatency | Seconds | Multi | Region, InstanceClass | ||
WriteThroughput | The average number of bytes written to disk per second | Bytes/Second | Multi | ReplicationInstanceIdentifier | ✔️ |
WriteThroughput | Bytes/Second | Multi | Region, ReplicationInstanceExternalResourceId | ||
WriteThroughput | Bytes/Second | Multi | Region | ||
WriteThroughput | Bytes/Second | Multi | Region, InstanceClass |
Limitations
To collect metrics about changes captured by the migration task (CDC metrics) on MySQL, the binary logging and automatic backup settings should be enabled.