We offer a cloud integration for reporting your GCP Redis data to our platform. Here we explain how to activate the integration and what data it collects.
Activate the integration
To enable the integration follow standard procedures to connect your GCP service.
Configuration and polling
You can change the polling frequency and filter data using configuration options.
Default polling information for the GCP Redis integration:
- New Relic polling interval: 5 minutes
Find and use data
To find your integration data, go to one.newrelic.com > All capabilities > Infrastructure > GCP and select the integration.
Data is attached to the following event types:
Entity | Event Type | Provider |
|---|---|---|
RedisInstance |
|
|
For more on how to use your data, see Understand and use integration data.
Metric data
This integration collects GCP Redis data for RedisInstance.
Redis RedisInstance data
Metric | Unit | Description |
|---|---|---|
| Count | Number of blocked clients. |
| Count | Number of client connections. |
| Count | Total number of calls for this command in one minute. |
| Microseconds | The amount of time in microseconds that this command took in the last second. |
| Count | Average time per call over 1 minute by command. |
| Milliseconds | Average TTL for keys in this database. |
| Count | Number of keys stored in this database. |
| Count | Number of keys with an expiration in this database. |
| Bytes | The number of bytes that replica is behind. |
| Bytes | The number of bytes that have been acknowledged by replicas. |
| Bytes | The number of bytes that master has produced and sent to replicas. To be compared with replication byte offset of replica. |
| Bytes | The number of bytes that have not been replicated to the replica. This is the difference between replication byte offset (master) and replication byte offset (replica). |
| Count | Returns a value indicating the node role. 1 indicates master and 0 indicates replica. |
| Seconds | Uptime in seconds. |
| Count | Cache Hit ratio as a fraction. |
| Count | Total number of connections accepted by the server. |
| s{CPU} | CPU-seconds consumed by the Redis server, broken down by system/user space and parent/child relationship. |
| Count | Number of evicted keys due to maxmemory limit. |
| Count | Total number of key expiration events. |
| Count | Number of successful lookup of keys in the main dictionary. |
| Count | Number of failed lookup of keys in the main dictionary. |
| Bytes | Maximum amount of memory Redis can consume. |
| Microseconds | The amount of time in microseconds the instance is in system memory overload mode. |
| Count | Memory usage as a ratio of maximum system memory. |
| Bytes | Total number of bytes allocated by Redis. |
| Count | Memory usage as a ratio of maximum memory. |
| Bytes | Total number of bytes sent to/from redis (includes bytes from commands themselves, payload data, and delimiters). |
| Count | Global number of pub/sub channels with client subscriptions. |
| Count | Global number of pub/sub pattern with client subscriptions. |
| Count | Number of connections rejected because of maxclients limit. |