New Relic infrastructure integrations now include an integration for AWS Keyspaces, sending its metric data to New Relic.
This document explains the integration's features, how to activate it, and what data can be reported.
Features
Collect and send telemetry data to New Relic from your Keyspaces using our integration. Monitor your services, query incoming data, and build dashboards to observe everything at a glance.
Activate integration
To enable this integration, see how to connect AWS services to New Relic.
Find and use data
To find your integration's metrics, go to one.newrelic.com > All capabilities > Metrics and events and filter by aws.cassandra.
Metric data
This New Relic infrastructure integration collects the following Amazon Keyspaces data:
Keyspaces Metric data
All imported data has one common dimension: TableName
Metric (min, max, average, count, sum) | Unit | Description |
|---|---|---|
| Bytes | The billable size of the table in bytes. |
| Count | The number of failed lightweight transaction (LWT) write requests. |
| Count | The number of read capacity units consumed over the specified time period. |
| Count | The number of write capacity units consumed over the specified time period. |
| Count | Requests to Amazon Keyspaces that exceed the per-connection request rate quota. |
| Count | The number of provisioned read capacity units for a table. |
| Count | The number of provisioned write capacity units for a table. |
| Count | Requests to Amazon Keyspaces that exceed the provisioned read capacity for a table, or account level quotas, request per connection quotas, or partition level quotas. |
| Millisecond | This metric only applies to multi-Region keyspaces and measures the time it took to replicate updates, inserts, or deletes from one replica table to another replica table in a multi-Region keyspace. |
| Count | The number of rows returned by multi-row SELECT queries during the specified time period. |
| Count | Requests to an Amazon Keyspaces storage partition that exceed the throughput capacity of the partition. |
| Count | The number of successful requests processed over the specified time period. |
| Milliseconds | The successful requests to Amazon Keyspaces during the specified time period. |
| Count | The requests to Amazon Keyspaces that generate a ServerError during the specified time period. |
| Count | The units consumed to delete tombstoned data when client-side timestamps are enabled. |
| Count | The units consumed to delete or update data in a row by using Time to Live (TTL). |
| Count | Requests to Amazon Keyspaces that generate an InvalidRequest error during the specified time period. |
| Count | Requests to Amazon Keyspaces that exceed the provisioned write capacity for a table, or account level quotas, request per connection quotas, or partition level quotas. |
The imported data shown in this table has no dimension:
Metric (min, max, average, count, sum) | Unit | Description |
|---|---|---|
| Count | The maximum number of read capacity units that can be used by a table of an account. |
| Count | The maximum number of write capacity units that can be used by a table of an account. |
| Percent | The percentage of provisioned read capacity units utilized by an account. |
| Percent | The percentage of provisioned write capacity units utilized by an account. |
| Percent | The percentage of provisioned read capacity units utilized by the highest provisioned read table of an account. |
| Percent | The percentage of provisioned write capacity utilized by the highest provisioned write table of an account. |
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 in Introduction to alerts.