Important
百度 据了解，2018年，西藏将实行粮食双增行动，确保粮食播种面积稳定在260万亩以上，产业化龙头企业总产值和农畜产品加工企业总产值均要提升15%左右。Enable the AWS CloudWatch Metric Streams integration to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option.
New Relic infrastructure integrations include an integration for reporting your Amazon Web Services RDS data to New Relic. This document explains how to activate this integration and describes the data that can be reported.
New Relic also offers an integration for enhanced RDS monitoring.
Features
Amazon's Relational Database Service (RDS) is a web service that makes it easier to set up, operate, and scale a relational database in the cloud. It provides cost-efficient, resizable capacity for an industry-standard relational database and manages common database administration tasks.
New Relic's RDS monitoring integration gathers metric and configuration data for the relational databases associated with your Amazon RDS account. Your RDS data is available in pre-built and you can also create custom queries and charts. You can create alert conditions for RDS data, and use the reported data to plan for future RDS capacity.
Activate integration
To enable this integration follow standard procedures to Connect AWS services to New Relic.
Configuration and polling
You can change the polling frequency and filter data using configuration options.
Default polling information for the Amazon RDS integration:
- New Relic polling interval: 5 minutes
- Amazon CloudWatch data interval: 1 minute for RDS instances; 5 minutes for RDS clusters
Find and use data
To view the RDS dashboard:
- Go to one.newrelic.com > All capabilities > Infrastructure > AWS.
- From the list of AWS services, scroll-down to RDS then click the RDS Dashboard link.
You can query and explore your data using the DatastoreSample event type, with a provider value of RdsDbInstance for DB instances, or RdsDbCluster for Aurora DB clusters.
For more on how to use your data, see Understand and use integration data.
Metric data
This integration collects Amazon RDS data for clusters and also for instances. Some RDS instance metrics are distinct for cluster instances and stand-alone instances.
RDS cluster metric data
Name | Description |
|---|---|
| Volume bytes used. |
| Volume read IOPs. |
| Volume write IOPs. |
RDS instance common metric data
Metric | Description |
|---|---|
| The number of CPU credits consumed during the specified period. |
| The number of CPU credits that an instance has accumulated. |
| The percentage of CPU used by a DB instance. |
| The number of connections to an instance. |
| The number of outstanding read/write requests waiting to access the disk. |
| The amount of available random access memory, in bytes. |
| The age of the oldest unvacuumed transaction ID, in transactions. |
| The amount of network throughput received from clients by each instance in the Aurora MySQL DB cluster, in bytes per second. |
| The amount of network throughput sent to clients by each instance in the Aurora DB cluster, in bytes per second. |
| The average amount of time taken per disk I/O operation, in seconds. |
| The average number of bytes read from disk per second. |
| The amount of swap space used on the Aurora PostgreSQL DB instance, in bytes. |
| The amount of disk space occupied by transaction logs on the Aurora PostgreSQL DB instance, in bytes. |
RDS cluster instance data
Metric | Description |
|---|---|
| The average number of current transactions executing on an Aurora database instance per second. |
| For an Aurora Replica, the amount of lag when replicating updates from the primary instance, in milliseconds. |
| The maximum amount of lag between the primary instance and each Aurora DB instance in the DB cluster, in milliseconds. |
| The minimum amount of lag between the primary instance and each Aurora DB instance in the DB cluster, in milliseconds. |
| The number of backtrack change records created over five minutes for your DB cluster. |
| The actual number of backtrack change records used by your DB cluster. |
| The difference between the target backtrack window and the actual backtrack window. |
| The number of times that the actual backtrack window is smaller than the target backtrack window for a given period of time. |
| The average number of transactions in the database that are blocked per second. |
| The percentage of requests that are served by the buffer cache. |
| The amount of latency for commit operations, in milliseconds. |
| The average number of commit operations per second. |
| The amount of latency for data definition language (DDL) requests, in milliseconds—for example, create, alter, and drop requests. |
| The average number of DDL requests per second. |
| The average number of deadlocks in the database per second. |
| The amount of latency for delete queries, in milliseconds. |
| The average number of delete queries per second. |
| The amount of latency for inserts, updates, and deletes, in milliseconds. |
| The average number of inserts, updates, and deletes per second. |
| The amount of time that the instance has been running, in seconds. |
| This metric, displayed under the SQL category of the latest metrics view in the Amazon RDS console, does not apply to Amazon Aurora. |
| The amount of storage available for temporary tables and logs, in bytes. |
| The amount of latency for insert queries, in milliseconds. |
| The average number of insert queries per second. |
| The average number of failed login attempts per second. |
| The amount of network throughput both received from and transmitted to clients by each instance in the Aurora MySQL DB cluster, in bytes per second. |
| The average number of queries executed per second. |
| The amount of lag in seconds when replicating updates from the primary RDS PostgreSQL instance to other nodes in the cluster. |
| The percentage of requests that are served by the Resultset cache. |
| The amount of latency for select queries, in milliseconds. |
| The average number of select queries per second. |
| Total number of connections to the database instance. |
| The amount of latency for update queries, in milliseconds. |
| The average number of update queries per second. |
| The number of billed read I/O operations from a cluster volume, reported at 5-minute intervals. |
| The number of write disk I/O operations to the cluster volume, reported at 5-minute intervals. |
RDS stand-alone instance data
Metric | Description |
|---|---|
| Specifies the allocated storage size, in bytes. Note this data doesn't come from an AWS CloudWatch metric, but from the |
| The amount of disk space occupied by binary logs on the master, in bytes. |
| The number of outstanding read/write requests waiting to access the disk. |
| The amount of storage available for tables and logs, in bytes. |
| The age of the oldest unvacuumed transaction ID, in transactions. |
| Shows how far behind in seconds the most lagging replica is in terms of WAL data received. |
| The average number of disk I/O operations per second. |
| The average amount of time taken per disk I/O operation. |
| The average number of bytes read from disk per second. |
| The amount of lag when replicating updates from the primary instance, in milliseconds. |
| The amount of disk space occupied by replication slots. |
| The amount of swap space used on the Aurora PostgreSQL DB instance, in bytes. |
| The amount of disk space occupied by transaction logs on the Aurora PostgreSQL DB instance. |
| How much storage is being used for WAL data. |
| The average number of disk I/O operations per second. |
| The average amount of time taken per disk I/O operation. |
| The average number of bytes written to disk per second. |