GCP Memorystore for Redis Standalone

GCP Memorystore for Redis Standalone provides a fully-managed service that is powered by the Redis in-memory data store to build application caches that provide sub-millisecond data access.

Cisco Cloud Observability supports monitoring the following GCP Memorystore for Redis entities:

Redis Instance: An in-memory Redis data store. Comprised of one or more Redis nodes.
Redis Node: Represents an actual Redis node, as part of a Memorystore for Redis standalone instance in GCP.

You must configure cloud connections to monitor this entity. See Configure Google Cloud Platform Connection.

Cisco Cloud Observability displays GCP entities on the Observe page. Metrics are displayed for specific entity instances in the list and detail views.

This document contains references to third-party documentation. Splunk AppDynamics does not own any rights and assumes no responsibility for the accuracy or completeness of such third-party documentation.

Detail View

To display the detail view of a GCP Memorystore for Redis Standalone entity:

Navigate to the Observe page.
Under Database & Storage, click GCP Redis Instances.
The list view now displays.
From the list, click a Name to display the detail view.
The detail view displays metrics, key performance indicators, and properties (attributes) related to the instance you selected.

Navigate to the Observe page.
Under Database & Storage, click GCP Redis Instances.
In the left-side Relationships panel, click GCP Redis Nodes.
The list view now displays.
Click a Name to display the detail view.
The detail view displays metrics, key performance indicators, and properties (attributes) related to the instance you selected.

Metrics and Key Performance Indicators

Cisco Cloud Observability displays the following metrics and key performance indicators (KPIs) for GCP Redis Instances and GCP Redis Nodes. See Google Cloud metrics.

The metrics for GCP Redis Instances are aggregated across all nodes under the same instance using the Cisco Cloud Observability platform. The metrics are not collected from GCP.

Display Name	Source Metric Name	Description
Connected Clients (Count)	`clients/connected`	The number of client connections.
Command Calls (Count)	`commands/calls`	Total number of calls for this command in one minute.
Command Call Total Time (us)	`commands/total_time`	The amount of time in microseconds that this command took in the last second.
Average Key TTL (s)	`keyspace/avg_ttl`	Average TTL for keys in this database.
Items (Count)	`keyspace/keys`	The number of keys stored in this database.
Keys With Expiration (Count)	`keyspace/keys_with_expiration`	The number of keys with an expiration in this database.
RDB Save In Progress (Boolean)	`persistence/rdb/bgsave_in_progress`	Flag indicating a RDB save is on-going.
RDB Enabled (Boolean)	`rdb/enabled`	Indicates if the snapshot is in RDB mode.
RDB Recovery Estimated Time (s)	`rdb/recovery/estimated_recovery_time`	Indicates the expected recovery time when using the last successful snapshot for recovery.
RDB Snapshot Attempts (Count)	`rdb/snapshot/attempt_count`	Indicates number of snapshot attempts every minute.
RDB Snapshot Elapsed Time (s)	`rdb/snapshot/elapsed_time`	Indicates increasing time elapsed while creating the current snapshot.
RDB Snapshot In Progress (Boolean)	`rdb/snapshot/in_progress`	Indicates if RDB snapshot is in progress. When the metric value is true, then an RDB snapshot is in progress.
RDB Snapshot Last Status	`rdb/snapshot/last_status`	Indicates status of the most recent snapshot attempt.
RDB Snapshot Last Status Age (s)	`rdb/snapshot/last_success_age`	Indicates time elapsed since the start of the last successful snapshot.
RDB Snapshot Last Success Duration (s)	`rdb/snapshot/last_success_duration`	Indicates the total time required to write the last successful snapshot, not including failed attempts.
RDB Snapshot Time Until Next Run (s)	`rdb/snapshot/time_until_next_run`	Seconds until the next scheduled snapshot.
Replication Lag (s)	`replication/master/slaves/lag`	The number of seconds that replica is lagging behind primary.
Slave Replication Offset (By)	`replication/master/slaves/offset`	The number of bytes that have been acknowledged by replicas.
Replication Bytes (By)	`replication/master_repl_offset`	The number of bytes that master has produced and sent to replicas. To be compared with replication byte offset of replica.
Replication Offset Difference (By)	`replication/offset_diff`	The largest number of bytes that have not been replicated across all replicas. This is the biggest difference between replication byte offset (master) and replication byte offset (replica) of all replicas.
Replication Role (Boolean)	`replication/role`	Returns a value indicating the node role. 1 indicates primary and 0 indicates replica.
Uptime (s)	`server/uptime`	Uptime in seconds.
Cache Hit Rate (%)	`stats/cache_hit_ratio`	Cache Hit ratio as a fraction.
Connections (Count)	`stats/connections/total`	Total number of connections accepted by the server.
CPU Usage (%)	`stats/cpu_utilization`	The percentage of CPU utilization of the Redis node.
Evictions (Count)	`stats/evicted_keys`	The number of evicted keys due to maxmemory limit.
Expired Keys (Count)	`stats/expired_keys`	Total number of key expiration events.
Key Stats (Count)	`stats/keyspace_hits` `stats/keyspace_misses`	The number of successful/failed lookup of keys in the main dictionary.
Maximum Memory (By)	`stats/memory/maxmemory`	Maximum amount of memory Redis can consume.
System Memory Usage Ratio (%)	`stats/memory/system_memory_usage_ratio`	Memory usage as a ratio of maximum system memory.
System Memory Usage (By)	`stats/memory/usage`	Total number of bytes allocated by Redis.
Memory Usage Ratio (%)	`stats/memory/usage_ratio`	Memory usage as a ratio of maximum memory.
Network Throughput (By)	`stats/network_traffic`	Total number of bytes sent to/from redis (includes bytes from commands themselves, payload data, and delimiters).
Pub/Sub Channels (Count)	`stats/pubsub/channels`	Global number of pub/sub channels with client subscriptions.
Pub/Sub Patterns (Count)	`stats/pubsub/patterns`	Global number of pub/sub pattern with client subscriptions.

Properties (Attributes)

Cisco Cloud Observability displays the following properties for GCP Memorystore for Redis Standalone.

Display Name	Source Property Name	Description
ID	`name`	The ID of the node. Internal, including the instance ID as a prefix.
Name	`displayName`	The display name of the instance.
Project ID	-	The ID of the GCP project.
Region	-	The location of the node.
Zone	`locationId`	Optional. The zone where the instance will be provisioned.
State	`state`	The current state of this instance.
Tier	`tier`	The service tier of the instance.
Current Location	`currentLocationId`	The current zone where the Redis primary node is located. In basic tier, this will always be the same as `location`. In standard tier, this can be the zone of any node in the instance.
Alternative Location	`alternativeLocationId`	Optional. If specified, at least one node will be provisioned in this zone in addition to the zone specified in `location`.
Redis Version	`redisVersion`	Optional. The version of Redis software. If not provided, the latest supported version will be used.
Reserved IP Range	`reservedIpRange`	Optional. For `DIRECT_PEERING` mode, the CIDR range of internal addresses that are reserved for this instance. Range must be unique and non-overlapping with existing subnets in an authorized network. For `PRIVATE_SERVICE_ACCESS` mode, the name of one allocated IP address ranges associated with this private service access connection. If not provided, the service will choose an unused /29 block; for example, 10.0.0.0/29 or 192.168.0.0/29. For `READ_REPLICAS_ENABLED`, the default block size is /28.
Secondary IP Range	`secondaryIpRange`	Optional. Additional IP range for node placement. Required when enabling read replicas on an existing instance. For `DIRECT_PEERING` mode, the value must be a CIDR range of size /28, or `auto`. For `PRIVATE_SERVICE_ACCESS` mode, the value must be the name of an allocated address range associated with the private service access connection, or `auto`.
Host	`host`	The hostname or IP address of the exposed Redis endpoint used by clients to connect to the service.
Port	`port`	The port number of the exposed Redis endpoint.
Create Time	`createTime`	The time the instance was created.
Status Message	`statusMessage`	Additional information about the current status of this instance, if available.
Memory Size	`memorySizeGb`	The Redis memory size in GiB.
Persistence IAM Identity	`persistenceIamIdentity`	The cloud IAM identity used by import/export operations to transfer data to and from Cloud Storage. The format is `serviceAccount:`. The value may change over time for a given instance, so it should be checked before each import/export operation.
Connect Mode	`connectMode`	The network connect mode of the Redis instance. If not provided, the connect mode defaults to `DIRECT_PEERING`.
Auth Enabled	`authEnabled`	Specifies whether OSS Redis AUTH is enabled for the instance. If set to `true`, AUTH is enabled on the instance. The default value is `false`, meaning AUTH is disabled.
Transit Encryption Mode	`transitEncryptionMode`	The TLS mode of the Redis instance. If not provided, TLS is disabled for the instance.
Replicas	`replicaCount`	The number of replica nodes.
Read Endpoint Host	`readEndpoint`	The hostname or IP address of the exposed read-only Redis endpoint. Standard tier only.
Read Endpoint Port	`readEndpointPort`	The port number of the exposed readonly redis endpoint. Standard tier only. Write requests should target `port`.
Read Replicas Mode	`readReplicasMode`	The read replicas mode for the instance. Defaults to `READ_REPLICAS_DISABLED`.
Persistence Mode	`persistenceConfig.persistenceMode`	Specifies whether persistence features are enabled.

Display Name	Source Property Name	Description
ID	-	The ID of the node. Internal, including the instance ID as a prefix.
Name	`displayName`	The display name of the instance.
Project ID	-	The ID of the GCP project.
Platform	-	The `gcp_redis_node` string, hardcoded.
Region	-	The location of the node.

Retention and Purge Time-To-Live (TTL)

For all cloud and infrastructure entities, the retention TTL is 180 minutes (3 hours) and the purge TTL is 525,600 minutes (365 days).

Third party names, logos, marks, and general references used in these materials are the property of their respective owners or their affiliates in the United States and/or other countries. Inclusion of such references are for informational purposes only and are not intended to promote or otherwise suggest a relationship between Splunk AppDynamics and the third party.