• EnglishEspañol日本語한국어Português
  • Log inStart now

Google Memorystore for Redis

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

GcpRedisInstanceSample

GcpRedisInstance

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

clients.Blocked

Count

Number of blocked clients.

clients.Connected

Count

Number of client connections.

commands.Calls

Count

Total number of calls for this command in one minute.

commands.TotalTime

Microseconds

The amount of time in microseconds that this command took in the last second.

commands.UsecPerCall

Count

Average time per call over 1 minute by command.

keyspace.AvgTtl

Milliseconds

Average TTL for keys in this database.

keyspace.Keys

Count

Number of keys stored in this database.

keyspace.KeysWithExpiration

Count

Number of keys with an expiration in this database.

replication.master.slaves.Lag

Bytes

The number of bytes that replica is behind.

replication.master.slaves.Offset

Bytes

The number of bytes that have been acknowledged by replicas.

replication.MasterReplOffset

Bytes

The number of bytes that master has produced and sent to replicas. To be compared with replication byte offset of replica.

replication.OffsetDiff

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).

replication.Role

Count

Returns a value indicating the node role. 1 indicates master and 0 indicates replica.

server.Uptime

Seconds

Uptime in seconds.

stats.CacheHitRatio

Count

Cache Hit ratio as a fraction.

stats.connections.Total

Count

Total number of connections accepted by the server.

stats.CpuUtilization

s{CPU}

CPU-seconds consumed by the Redis server, broken down by system/user space and parent/child relationship.

stats.EvictedKeys

Count

Number of evicted keys due to maxmemory limit.

stats.ExpiredKeys

Count

Total number of key expiration events.

stats.KeyspaceHits

Count

Number of successful lookup of keys in the main dictionary.

stats.KeyspaceMisses

Count

Number of failed lookup of keys in the main dictionary.

stats.memory.Maxmemory

Bytes

Maximum amount of memory Redis can consume.

stats.memory.SystemMemoryOverloadDuration

Microseconds

The amount of time in microseconds the instance is in system memory overload mode.

stats.memory.SystemMemoryUsageRatio

Count

Memory usage as a ratio of maximum system memory.

stats.memory.Usage

Bytes

Total number of bytes allocated by Redis.

stats.memory.UsageRatio

Count

Memory usage as a ratio of maximum memory.

stats.NetworkTraffic

Bytes

Total number of bytes sent to/from redis (includes bytes from commands themselves, payload data, and delimiters).

stats.pubsub.Channels

Count

Global number of pub/sub channels with client subscriptions.

stats.pubsub.Patterns

Count

Global number of pub/sub pattern with client subscriptions.

stats.RejectConnections

Count

Number of connections rejected because of maxclients limit.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.