New Relic integrations with the Google Cloud Platform (GCP) include one that reports Google Memorystore for Valkey data to New Relic. This document explains how to activate the GCP Memorystore for Valkey integration and describes the data it reports.
Features
Memorystore for Valkey is Google Cloud's fully managed Valkey service, providing an open-source Redis-compatible in-memory data store. New Relic Memorystore for Valkey integration collects instance-level and per-node metrics across CPU, memory, clients, keyspace, persistence, and network for each Valkey deployment.
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 Valkey 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 Valkey resources 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 Valkey 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 metrics documentation for the complete list.
New Relic builds each metric name from the Google Cloud metric type: it removes .googleapis.com/, replaces each / with ., and adds the gcp. prefix. For example, memorystore.googleapis.com/instance/commandstats/total_calls_count becomes gcp.memorystore.instance.commandstats.total_calls_count.
Google reports some metrics separately for each replication role. These metrics carry the metric.role attribute, with the value primary or replica.
Entities
Metric data
Key metrics — Instance
Metric name | Unit | Description |
|---|---|---|
| Percent | Mean CPU utilization across nodes of the Valkey instance. |
| Percent | Maximum CPU utilization observed across nodes of the Valkey instance. |
| Percent | Mean memory utilization across nodes of the Valkey instance. |
| Percent | Maximum memory utilization observed across nodes of the Valkey instance. |
| Bytes | Configured memory size for the Valkey instance. |
| Count | Total number of clients connected to the Valkey instance. |
| Count | Number of commands processed by the Valkey instance, faceted by the |
| Microseconds | Total time spent processing commands on the Valkey instance, faceted by the |
| Count | Total number of keys stored on the Valkey instance. |
| Count | Total number of key expiration events on the Valkey instance. |
| Count | Total number of keys evicted from the Valkey instance due to memory capacity. |
| Bytes | Mean replication offset difference across the Valkey instance. |
| Bytes | Maximum replication offset difference across the Valkey instance. |
Key metrics — Instance Node
Metric name | Unit | Description |
|---|---|---|
| Percent | CPU utilization on the Valkey node. |
| Percent | Memory utilization on the Valkey node. |
| Bytes | Memory currently in use on the Valkey node. |
| Count | Number of clients connected to the Valkey node. |
| Count | Number of calls for each command on the Valkey node, faceted by the |
| Count | Number of keys stored on the Valkey node. |
| Bytes | Incoming network bytes received by the Valkey node. |
| Bytes | Outgoing network bytes sent from the Valkey node. |
| Bytes | Replication offset of the Valkey node. |
For the complete list of Memorystore for Valkey metrics, see Google's Memorystore metrics documentation.