중요
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 Amazon DynamoDB data to New Relic. This document explains how to activate this integration and describes the data that can be reported.
Features
Amazon DynamoDB is a fully managed NoSQL cloud database that supports both document and key-value store models. With the New Relic DynamoDB Integration, you can quickly understand how request latency or errors are affecting your environment. You'll receive metrics about how the database is performing, service status, and host metadata.
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 DynamoDB integration:
- New Relic polling interval: 5 minutes
- Amazon CloudWatch data interval: 1 minute or 5 minutes, depending on statistic
View and use data
To view and use your integration data, go to one.newrelic.com > All capabilities > Infrastructure > AWS and select one of the Amazon DynamodDB integration links.
You can query and explore your data using the DatastoreSample
event type, with a provider
value of DynamoDbTable
for DynamoDB tables, DynamoDbRegion
for regions, or DynamoDbGlobalSecondaryIndex
for DynamoDB global secondary indexes.
Metric data
The New Relic Amazon DynamoDB integration collects the following metric data:
팁
Data indicated with an asterisk *
is only fetched if extended inventory collection is on.
DynamoDbTable
Metric | Description |
---|---|
| Elapsed time for successful BatchGetItem operation requests, in milliseconds. |
| BatchGetItem operation requests that exceed the provisioned throughput limits on a table. |
| Elapsed time for successful BatchWriteItem operation requests, in milliseconds. |
| BatchWriteItem operation requests that exceed the provisioned throughput limits on a table. |
| The number of failed attempts to perform conditional writes. |
| The number of read capacity units consumed over the specified time period, to track how much of provisioned throughput is used. |
| The number of write capacity units consumed over the specified time period, to track how much of provisioned throughput is used. |
| Elapsed time for successful Delete operation requests, in milliseconds. |
| Delete operation requests that exceed the provisioned throughput limits on a table. |
| Elapsed time for successful Get operation requests, in milliseconds. |
| Get operation requests that exceed the provisioned throughput limits on a table. |
| The number of item updates that are written to one replica table, but that have not yet been written to another replica in the global table. |
| The number of provisioned read capacity units for a table. |
| The number of provisioned write capacity units for a table. |
| Elapsed time for successful Put operation requests, in milliseconds. |
| Put operation requests that exceed the provisioned throughput limits on a table. |
| The number of items returned by Query operations. |
| Elapsed time for successful Query operation requests, in milliseconds. |
| Query operation requests that exceed the provisioned throughput limits on a table. |
| Requests to DynamoDB that exceed the provisioned read capacity units for a table. |
| The elapsed time between an updated item appearing in the DynamoDB stream for one replica table, and that item appearing in another replica in the global table, in milliseconds. |
| The number of items returned by Scan operations. |
| Elapsed time for successful Scan operation requests, in milliseconds. |
| Scan operation requests that exceed the provisioned throughput limits on a table. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Elapsed time for successful Update operation requests, in milliseconds. |
| Update operation requests that exceed the provisioned throughput limits on a table. |
| Requests to DynamoDB that exceed the provisioned write capacity units for a table. |
DynamoDbRegion
This sample limits the data to a particular AWS region. It is used with metrics originating from replica tables within a DynamoDB global table.
Metric | Description |
---|---|
| Requests that generate an HTTP 500 status code. |
| Requests that generate an HTTP 400 status code |
DynamoDbGlobalSecondaryIndex
Metric | Description |
---|---|
| The number of read capacity units consumed over the specified time period, to track how much of provisioned throughput is used. |
| The number of write capacity units consumed over the specified time period, to track how much of provisioned throughput is used. |
| The number of write capacity units consumed when adding a new global secondary index to a table. |
| The percentage of completion when a new global secondary index is being added to a table. |
| The number of write throttle events that occur when adding a new global secondary index to a table. |
| The number of provisioned read capacity units for a global secondary index. |
| The number of provisioned write capacity units for a table. |
| Requests to DynamoDB that exceed the provisioned read capacity units for a table. |
| Requests to DynamoDB that exceed the provisioned write capacity units for a table. |