You can now integrate the infrastructure agent with AWS Database Migration Service, letting you send its metric data to New Relic. Monitor your services, query incoming data, and build dashboards to observe everything at a glance.
To enable this integration, follow our instructions to connect AWS services to New Relic. Once enabled, you can find your integration's metrics at one.newrelic.com > Metrics and events and filter by aws.dms.
Metric data
This New Relic infrastructure integration collects the following Amazon Database Migration Service data:
All imported data has one common dimension: ReplicationInstanceIdentifier
Replication Instance Metrics data
Metric (min, max, average, count, sum) | Unit | Description |
|---|---|---|
| Bytes | An estimate of how much memory is available for starting new applications, without swapping. |
| Percent | The percentage of CPU maximally allocated for the task (0 means no limit). |
| Count | The percentage of allocated vCPU (virtual CPU) currently in use on the instance. |
| Count | The number of outstanding read/write requests (I/Os) waiting to access the disk. |
| Bytes | The amount of available storage space. |
| Bytes | The amount of physical memory available for use by applications, page cache, and for the kernel’s own data structures. |
| Bytes | The amount of available random access memory. |
| MiB | The maximum allocation of memory for the task (0 means no limits). |
| Count/Second | The average number of disk write I/O operations per second. |
| Count/Second | The average number of disk read I/O operations per second. |
| Bytes/Second | The average number of bytes write from disk per second. |
| Bytes/Second | The average number of bytes read from disk per second. |
| Milliseconds | The average amount of time taken per disk I/O (output) operation. |
| Milliseconds | The average amount of time taken per disk I/O (input) operation. |
| Bytes | The amount of swap space used on the replication instance. |
| Bytes/second | 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 | The incoming (Receive) network traffic on the replication instance, including both customer database traffic and AWS DMS traffic used for monitoring and replication. |
Replication Task Metrics data
Metric (min, max, average, count, sum) | Unit | Description |
|---|---|---|
| KB/Second | Outgoing data transmitted from a full load for the target. |
| Rows/Second | Outgoing changes from a full load for the target. |
| Count | The total number of change events at a point-in-time that are waiting to be applied to the target. |
| Count | Amount of rows accumulating in a memory and waiting to be committed from the source. |
| Count | Amount of rows accumulating in a memory and waiting to be committed to the target. |
| Count | Amount of rows accumulating on disk and waiting to be committed from the source. |
| Count | Amount of rows accumulating on disk and waiting to be committed to the target. |
| KB/Second | Outgoing data transmitted for the target. |
| Rows/Second | Incoming task changes from the source. |
| Rows/Second | Outgoing task changes for the target. |
| Seconds | The gap between the last event captured from the source endpoint and current system time stamp of the AWS DMS instance. |
| Seconds | The gap between the first event timestamp waiting to commit on the target and the current timestamp of the AWS DMS instance. |
| Megabytes | The control group (cgroup) memory.usage_in_bytes consumed by a task. |
Create alerts
You can set up to notify you if there are any changes. For example, you can set up an alert to notify relevant parties of critical or fatal errors.
Learn more about creating alerts here.