Join us at the Dash conference! July 16-17, NYC

Google Cloud Memorystore for Redis

Crawler Crawler

Overview

Google Cloud Memorystore for Redis provides a fully managed in-memory data store service built on scalable, secure, and highly available infrastructure.

Use the Datadog Google Cloud Platform integration to collect metrics from Google Cloud Memorystore for Redis.

Setup

Installation

If you haven’t already, set up the Google Cloud Platform integration first. There are no other installation steps.

Data Collected

Metrics

gcp.redis.clients.blocked
(gauge)
Number of blocked clients
gcp.redis.clients.connected
(gauge)
Number of client connections
shown as connection
gcp.redis.commands.calls
(count)
Total number of calls for this command
gcp.redis.commands.total_time
(gauge)
The amount of time in microseconds that this command took in the last second
shown as microsecond
gcp.redis.commands.usec_per_call
(gauge)
Average time per call over 1 minute by command
shown as second
gcp.redis.keyspace.avg_ttl
(gauge)
Average TTL for keys in this database
shown as millisecond
gcp.redis.keyspace.keys_with_expiration
(gauge)
Number of keys with an expiration in this database
shown as key
gcp.redis.keyspace.keys
(gauge)
Number of keys stored in this database
shown as key
gcp.redis.persistence.rdb.bgsave_in_progress
(gauge)
Flag indicating a RDB save is on-going
gcp.redis.replication.master.slaves.lag
(gauge)
The number of bytes that replica is behind.
shown as byte
gcp.redis.replication.master.slaves.offset
(gauge)
The number of bytes that have been acknowledged by replicas.
shown as byte
gcp.redis.replication.master_repl_offset
(gauge)
The number of bytes that master has produced and sent to replicas. To be compared with replication byte offset of replica.
shown as byte
gcp.redis.replication.offset_diff
(gauge)
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).
shown as byte
gcp.redis.replication.role
(gauge)
Returns a value indicating the node role. 1 indicates master and 0 indicates replica.
gcp.redis.server.uptime
(gauge)
Uptime in seconds
shown as second
gcp.redis.stats.cache_hit_ratio
(gauge)
Cache Hit ratio as a fraction
gcp.redis.stats.connections.total
(gauge)
Total number of connections accepted by the server
shown as connection
gcp.redis.stats.cpu_utilization
(count)
CPU, in utilization percentage, consumed by the Redis server broken down by System/User and Parent/Child relationship
shown as percent
gcp.redis.stats.evicted_keys
(count)
Number of evicted keys due to maxmemory limit
shown as key
gcp.redis.stats.expired_keys
(count)
Total number of key expiration events
shown as key
gcp.redis.stats.keyspace_hits
(count)
Number of successful lookup of keys in the main dictionary
shown as key
gcp.redis.stats.keyspace_misses
(count)
Number of failed lookup of keys in the main dictionary
shown as key
gcp.redis.stats.memory.maxmemory
(gauge)
Maximum amount of memory Redis can consume
shown as byte
gcp.redis.stats.memory.system_memory_usage_ratio
(gauge)
Memory usage as a ratio of maximum system memory
shown as fraction
gcp.redis.stats.memory.usage_ratio
(gauge)
Memory usage as a ratio of maximum memory
shown as fraction
gcp.redis.stats.memory.usage
(gauge)
Total number of bytes allocated by Redis
shown as byte
gcp.redis.stats.network_traffic
(count)
Total number of bytes sent to/from redis (includes bytes from commands themselves, payload data, and delimiters)
shown as byte
gcp.redis.stats.pubsub.channels
(gauge)
Global number of pub/sub channels with client subscriptions
gcp.redis.stats.pubsub.patterns
(gauge)
Global number of pub/sub pattern with client subscriptions
gcp.redis.stats.reject_connections_count
(count)
Number of connections rejected because of maxclients limit
shown as connection

Events

The Google Cloud Memorystore for Redis integration does not include any events.

Service Checks

The Google Cloud Memorystore for Redis integration does not include any service checks.

Troubleshooting

Need help? Contact Datadog support.