Important
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 offers an integration for reporting your AWS AppSync data. This document explains how to activate this integration and describes the data that can be reported.
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 AWS AppSync integration:
- New Relic polling interval: 5 minutes
- Amazon CloudWatch data interval: 1 minute
Find and use data
To find your integration data in the infrastructure UI, go to one.newrelic.com > All capabilities > Infrastructure > AWS and select an integration.
You can query and explore your data using this event type:
Entity | Event Type | Provider |
---|---|---|
Api |
|
|
For more on how to use your data, see New Relic data types.
Metric data
This integration collects AWS AppSync data for Api.
AppSync Api data
Metric | Unit | Description |
---|---|---|
| Count | The number of errors captured as a result of invalid requests due to incorrect client configuration. Typically, these errors happen anywhere outside of the GraphQL execution. For example, this could be an incorrect JSON payload or an incorrect query in the request, when the service is throttled, or even a potential misconfiguration on the Auth settings. |
| Count | Errors encountered during the execution of a GraphQL query. For example, this could occur when a query request is initiated for an empty or incorrect schema, if the Amazon Cognito user pool ID or AWS Region is invalid. Alternatively, this could also happen if AWS AppSync encounters an issue during an execution of a request. |
| Milliseconds | The time between when AWS AppSync receives a request from a client and when it returns a response to the client. This doesn't include the network latency encountered for a response to reach the end devices. |