Monitor GCP Memorystore for Redis Metrics and Logs

One-Click Integration

SigNoz deploys and manages the Collector for you. You turn the service on in SigNoz, and the SigNoz agent sets up metrics and logs collection in the background. Collects metrics and logs.

Prerequisites

• Your GCP project is connected with One-Click Integration.
• Your Memorystore for Redis instances run in that same project. The agent monitors only the project it's deployed in.

Step 1: Turn on the service in SigNoz

1. In SigNoz, go to Integrations > Google Cloud Platform.
2. Select GCP Memorystore Redis from the service list.
3. Turn on Metric Collection, Log Collection, or both.
4. Click Save.

The agent picks up the change within about 30 seconds and updates the Collector and the log sink for you. There's no Collector config to edit.

Step 2: Turn on the optional logs in GCP

Logs for instance changes and maintenance flow with no extra work. Logs for reading instance details, such as listing instances or fetching the AUTH string, are off by default. To collect them, turn on Data Access audit logs for Memorystore for Redis in your project.

Skip this step if you only need metrics and instance change logs.

Validate

1. Wait about 10 minutes for the first metrics to arrive.

2. In SigNoz, go to Dashboards and open GCP Memorystore Redis Overview. Panels should start filling in.

3. If you turned on Log Collection, open Logs in SigNoz and start with this filter to find your project's logs:

   Copy

   gcp.project = '<deployment-project-id>' AND gcp.resource_type = 'redis_instance'

   Log entries appear within a few minutes of the next instance change or maintenance event. If you don't see maintenance logs, drop the gcp.resource_type part of the filter.

   Verify these values:

   • <deployment-project-id>: the GCP project you connected with One-Click Integration.

Manual Setup

You run the OpenTelemetry Collector in your own GCP project and add Memorystore metrics to its configuration. You control which metrics are pulled and how often. Collects metrics, and logs if you set up the log pipeline.

Complete the GCP integration setup once, then follow the steps below for each project that hosts Redis instances.

Prerequisites

Before configuring this service, complete the shared GCP integration setup:

• Your GCP account is connected in SigNoz, and the project running your Redis instances is in Projects to Monitor.
• The OpenTelemetry Collector is deployed and running.
• The signoz-integration-collector service account has roles/monitoring.viewer on the project that hosts the instances. See Create a service account.
• The Cloud Monitoring API is enabled in that project.
• For logs only: the Cloud Logging API is enabled in that project, and you have finished steps 1 to 5 of Collect logs.

Step 1: Enable the service in SigNoz

1. In SigNoz, go to Integrations > Google Cloud Platform.
2. Select GCP Memorystore Redis from the service list.
3. Toggle Metric Collection on to activate the pre-built dashboard. Toggle Log Collection if you also want to send logs.
4. Open the Data Collected tab and note the metrics listed there. These are the metrics the dashboard's panels query.

Step 2: Add the metrics to your Collector config

Open the otel-collector-config.yaml you created in Deploy the Collector and add the Memorystore metric names to the metrics_list of the googlecloudmonitoring receiver for the project your instances run in. Only the metrics_list shown below changes; leave the rest of the file as is:

receivers:
  googlecloudmonitoring:
    project_id: "<monitored-project-id>"
    collection_interval: 300s   # 5 minutes; minimum is 60s
    metrics_list:
      # Availability
      - metric_name: "redis.googleapis.com/server/uptime"
      # Compute and memory
      - metric_name: "redis.googleapis.com/stats/cpu_utilization_main_thread"
      - metric_name: "redis.googleapis.com/stats/memory/usage_ratio"
      - metric_name: "redis.googleapis.com/stats/memory/system_memory_usage_ratio"
      # Clients
      - metric_name: "redis.googleapis.com/clients/connected"
      - metric_name: "redis.googleapis.com/clients/blocked"
      - metric_name: "redis.googleapis.com/stats/reject_connections_count"
      # Keyspace and cache effectiveness
      - metric_name: "redis.googleapis.com/keyspace/keys"
      - metric_name: "redis.googleapis.com/stats/cache_hit_ratio"
      # Commands
      - metric_name: "redis.googleapis.com/commands/calls"
      - metric_name: "redis.googleapis.com/commands/usec_per_call"

Verify these values:

• <monitored-project-id>: The GCP project that hosts your Redis instances. It must be one of the entries in your Projects to Monitor list.

Step 3: Apply the configuration

The Collector loads its config from the signoz-integration-collector-config secret, so a config change needs a new secret version and a redeploy:

1. Save your updated otel-collector-config.yaml.
2. Add a new secret version (step 2 of Deploy the Collector).
3. Redeploy the Cloud Run service (step 3).

Step 4: Send logs (optional)

To also send Memorystore audit and maintenance logs to SigNoz, follow Collect logs to set up the Pub/Sub topic, the push subscription, and the logs receiver. In step 6, Create a log sink, use this filter:

resource.type="redis_instance"
  OR (protoPayload.serviceName="redis.googleapis.com"
    AND protoPayload.methodName:".CloudRedis.")
  OR (log_id("maintenance.googleapis.com/activity_log")
    AND labels.activity_type_name:"CloudRedisRollout")

See Logs under What's collected for what this filter picks up and which logs need a setting in GCP first.

Validate

1. Wait one or two collection intervals (up to about 5 minutes with the default 300s).
2. In SigNoz, go to Dashboards and open the GCP Memorystore Redis Overview dashboard. Panels should start filling in.
3. To check a single metric, open Metrics Explorer and query redis.googleapis.com/stats/memory/usage_ratio.
4. For logs, open Logs and filter on gcp.resource_type = 'redis_instance'.