aws.appsync.4xxerror
(count) | The number of errors captured as a result of invalid requests due to incorrect client configuration.
Shown as error |
aws.appsync.5xxerror
(count) | Errors encountered during the execution of a GraphQL query.
Shown as error |
aws.appsync.active_connections
(count) | The number of concurrent WebSocket connections from clients to AWS AppSync in 1 minute. |
aws.appsync.connect_server_error
(count) | The number of errors that originated from AWS AppSync while processing connections. This is known to happen when an unexpected server-side issue occurs.
Shown as error |
aws.appsync.connect_success
(count) | The number of successful WebSocket connections to AWS AppSync. It is possible to have connections without subscriptions.
Shown as success |
aws.appsync.connection_duration
(count) | The amount of time that the connection stays open.
Shown as millisecond |
aws.appsync.disconnect_client_error
(count) | The number of client errors that originated from AWS AppSync while disconnecting WebSocket connections.
Shown as error |
aws.appsync.disconnect_server_error
(count) | The number of server errors that originated from AWS AppSync while disconnecting WebSocket connections.
Shown as error |
aws.appsync.disconnect_success
(count) | The number of successful WebSocket disconnections from AWS AppSync.
Shown as success |
aws.appsync.latency
(gauge) | The average 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.
Shown as millisecond |
aws.appsync.latency.maximum
(gauge) | The maximum 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.
Shown as millisecond |
aws.appsync.latency.p90
(gauge) | The 90th percentile 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.
Shown as millisecond |
aws.appsync.publish_data_message_client_error
(count) | The number of subscription event messages that failed to publish because of client-side errors.
Shown as error |
aws.appsync.publish_data_message_server_error
(count) | The number of errors that originated from AWS AppSync while publishing subscription event messages. This is known to happen when an unexpected server-side issue occurs.
Shown as error |
aws.appsync.publish_data_message_size
(gauge) | The size of subscription event messages published.
Shown as byte |
aws.appsync.publish_data_message_success
(count) | The number of subscription event messages that were successfully published.
Shown as success |
aws.appsync.requests
(count) | The number of requests (queries + mutations) that all APIs in your account have processed.
Shown as request |
aws.appsync.subscribe_client_error
(count) | The number of subscriptions that were rejected by AWS AppSync because of client-side errors. This can occur when a JSON payload is incorrect, the service is throttled, or the Authorization settings are misconfigured.
Shown as error |
aws.appsync.subscribe_server_error
(count) | The number of errors that originated from AWS AppSync while processing subscriptions. This is known to happen when an unexpected server-side issue occurs.
Shown as error |
aws.appsync.subscribe_success
(count) | The number of subscriptions that were successfully registered to AWS AppSync through WebSocket. It is possible to have connections without subscriptions, but it isn’t possible to have subscriptions without connections.
Shown as success |
aws.appsync.unsubscribe_client_error
(count) | The number of unsubscriptions that were rejected by AWS AppSync because of client-side errors.
Shown as error |
aws.appsync.unsubscribe_server_error
(count) | The number of errors that originated from AWS AppSync while processing unsubscriptions. This is known to happen when an unexpected server-side issue occurs.
Shown as error |
aws.appsync.unsubscribe_success
(count) | The number of unsubscriptions that were successfully processed from AWS AppSync.
Shown as success |
aws.appsync.active_connections.sum
(count) | The sum of concurrent WebSocket connections from clients to AWS AppSync in 1 minute. |
aws.appsync.active_subscriptions
(count) | The number of concurrent subscriptions from clients in 1 minute. |
aws.appsync.active_subscriptions.sum
(count) | The sum of concurrent subscriptions from clients in 1 minute. |
aws.appsync.connect_client_error
(count) | The number of WebSocket connections that were rejected by AWS AppSync because of client-side errors. This could imply that the service is throttled or the Authorization settings are misconfigured.
Shown as error |
aws.appsync.connect_client_error.sum
(count) | The sum of WebSocket connections that were rejected by AWS AppSync because of client-side errors. This could imply that the service is throttled or the Authorization settings are misconfigured.
Shown as error |
aws.appsync.connect_server_error.sum
(count) | The sum of errors that originated from AWS AppSync while processing connections. This is known to happen when an unexpected server-side issue occurs.
Shown as error |
aws.appsync.connect_success.sum
(count) | The sum of successful WebSocket connections to AWS AppSync. It is possible to have connections without subscriptions.
Shown as success |
aws.appsync.disconnect_client_error.sum
(count) | The sum of client errors that originated from AWS AppSync while disconnecting WebSocket connections.
Shown as error |
aws.appsync.disconnect_server_error.sum
(count) | The sum of server errors that originated from AWS AppSync while disconnecting WebSocket connections.
Shown as error |
aws.appsync.disconnect_success.sum
(count) | The sum of successful WebSocket disconnections from AWS AppSync.
Shown as success |
aws.appsync.publish_data_message_client_error.sum
(count) | The sum of subscription event messages that failed to publish because of client-side errors.
Shown as error |
aws.appsync.publish_data_message_server_error.sum
(count) | The number of errors that originated from AWS AppSync while publishing subscription event messages. This is known to happen when an unexpected server-side issue occurs.
Shown as error |
aws.appsync.publish_data_message_success.sum
(count) | The sum of subscription event messages that were successfully published.
Shown as success |
aws.appsync.subscribe_client_error.sum
(count) | The sum of subscriptions that were rejected by AWS AppSync because of client-side errors. This can occur when a JSON payload is incorrect, the service is throttled, or the Authorization settings are misconfigured.
Shown as error |
aws.appsync.subscribe_server_error.sum
(count) | The sum of errors that originated from AWS AppSync while processing subscriptions. This is known to happen when an unexpected server-side issue occurs.
Shown as error |
aws.appsync.subscribe_success.sum
(count) | The sum of subscriptions that were successfully registered to AWS AppSync through WebSocket. It is possible to have connections without subscriptions, but it isn’t possible to have subscriptions without connections.
Shown as success |
aws.appsync.unsubscribe_client_error.sum
(count) | The sum of unsubscriptions that were rejected by AWS AppSync because of client-side errors.
Shown as error |
aws.appsync.unsubscribe_server_error.sum
(count) | The sum of errors that originated from AWS AppSync while processing unsubscriptions. This is known to happen when an unexpected server-side issue occurs.
Shown as error |
aws.appsync.unsubscribe_success.sum
(count) | The sum of unsubscriptions that were successfully processed from AWS AppSync.
Shown as success |
