New Relic integrations with the Google Cloud Platform (GCP) include one that reports Google Memorystore for Redis data to New Relic. This document explains how to activate the GCP Memorystore for Redis integration and describes the data it reports.
Features
Memorystore for Redis is Google Cloud's fully managed Redis service. New Relic Memorystore for Redis integration collects CPU, memory, network, keyspace, persistence, replication, and command-throughput metrics for each Redis instance.
Activate integration
To enable the integration, follow standard procedures to connect your GCP service to New Relic:
Polling frequency
New Relic integrations query your GCP services according to a polling interval that varies by integration. The polling frequency for Google Memorystore for Redis is 5 minutes. The resolution is 1 data point every minute.
Workload Identity Federation
Find and use data
After you enable the integration, your Memorystore for Redis instances appear as entities in the New Relic entity explorer. To see dashboards and manage services, go to one.newrelic.com > All capabilities > Infrastructure > GCP.
All Memorystore for Redis metrics available in GCP Cloud Monitoring are collected as dimensional metrics in the Metric event type. Additional metrics beyond this table are collected automatically. See Google's Memorystore for Redis metrics documentation for the complete list.
Entities
Metric data
Key metrics — Redis Instance
Metric name | Unit | Description |
|---|---|---|
| Seconds | CPU-seconds consumed by the Redis instance. |
| Percent | Fraction of memory currently in use by the Redis instance. |
| Bytes | Memory used by the Redis instance. |
| Bytes | Configured memory size limit for the Redis instance. |
| Percent | Fraction of read commands that resulted in cache hits. |
| Count | Number of client connections to the Redis instance. |
| Bytes | Total network bytes transferred by the Redis instance. |
| Count | Number of keys that have expired on the Redis instance. |
| Count | Number of keys evicted from the Redis instance due to memory pressure. |
| Count | Number of Redis commands processed by the instance, faceted by command name. |
| Microseconds | Total time spent processing Redis commands, faceted by command name. |
| Bytes | Replication offset lag between the primary and replica. |
Key metrics — Redis Cluster
Metric name | Unit | Description |
|---|---|---|
| Percent | Average CPU utilization across all nodes in the Redis Cluster. |
| Percent | Maximum CPU utilization observed across nodes in the Redis Cluster. |
| Percent | Average memory utilization across all nodes in the Redis Cluster. |
| Percent | Maximum memory utilization observed across nodes in the Redis Cluster. |
| Count | Total number of commands processed by the Redis Cluster, faceted by command. |
| Count | Total number of clients connected to the Redis Cluster. |
| Seconds | Average TTL of keys in the Redis Cluster keyspace. |
| Count | Total number of keys stored in the Redis Cluster. |
Key metrics — Redis Cluster Node
Metric name | Unit | Description |
|---|---|---|
| Percent | CPU utilization on the Redis Cluster node. |
| Percent | Memory utilization on the Redis Cluster node. |
| Count | Number of clients connected to the Redis Cluster node. |
| Count | Number of commands processed by the Redis Cluster node, faceted by command. |
| Count | Number of keys stored on the Redis Cluster node. |
| Bytes | Network bytes received by the Redis Cluster node. |
| Bytes | Network bytes sent by the Redis Cluster node. |
For the complete list of Memorystore for Redis metrics, see Google's Memorystore for Redis metrics documentation.
Service account or user account
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. |