Redis

The Redis integration collects metrics related to performance and usage.Performance metrics focus on CPU, memory, and network throughput, and usagemetrics focus on keys, commands, and replication. The integration also collectsRedis logs and parses them into a JSON payload. During this process, thesymbols for role and level are transformed into a human readable format.

For more information about Redis, see theRedis documentation.

Prerequisites

To collect Redis telemetry, you mustinstall the Ops Agent:

  • For metrics, install version 2.7.0 or higher.
  • For logs, install version 2.5.0 or higher.

This integration supports Redis version 6.2.

Configure the Ops Agent for Redis

Following the guide toConfigure the OpsAgent, add the required elementsto collect telemetry from Redis instances, andrestart the agent.

Example configuration

The following commands create the configuration to collect and ingest telemetryfor Redis:

#ConfiguresOpsAgenttocollecttelemetryfromtheapp.Youmustrestarttheagentfortheconfigurationtotakeeffect.set-e#Checkifthefileexistsif[!-f/etc/google-cloud-ops-agent/config.yaml];then#Createthefileifitdoesn'texist.sudomkdir-p/etc/google-cloud-ops-agentsudotouch/etc/google-cloud-ops-agent/config.yamlfi#Createabackupoftheexistingfilesoexistingconfigurationsarenotlost.sudocp/etc/google-cloud-ops-agent/config.yaml/etc/google-cloud-ops-agent/config.yaml.bak#ConfiguretheOpsAgent.sudotee/etc/google-cloud-ops-agent/config.yaml >/dev/null <<EOFmetrics:receivers:redis:type:redisservice:pipelines:redis:receivers:-redislogging:receivers:redis:type:redisservice:pipelines:redis:receivers:-redisEOF

For these changes to take effect, you must restart the Ops Agent:

Linux

  1. To restart the agent, run the following command on your instance:
    sudo systemctl restart google-cloud-ops-agent
  2. To confirm that the agent restarted, run the following command and verify that the components "Metrics Agent" and "Logging Agent" started:
    sudo systemctl status "google-cloud-ops-agent*"

Windows

  1. Connect to your instance using RDP or a similar tool and login to Windows.
  2. Open a PowerShell terminal with administrator privileges by right-clicking the PowerShell icon and selectingRun as Administrator
  3. To restart the agent, run the following PowerShell command:
    Restart-Service google-cloud-ops-agent -Force
  4. To confirm that the agent restarted, run the following command and verify that the components "Metrics Agent" and "Logging Agent" started:
    Get-Service google-cloud-ops-agent*

Configure logs collection

To ingest logs from Redis, you must create a receiver for the logsthat Redis produces and then create a pipeline for the new receiver.

To configure a receiver for yourredis logs, specify the followingfields:

FieldDefaultDescription
exclude_pathsA list of filesystem path patterns to exclude from the set matched byinclude_paths.
include_paths[/var/log/redis/redis-server.log, /var/log/redis_6379.log, /var/log/redis/redis.log, /var/log/redis/default.log, /var/log/redis/redis_6379.log]A list of filesystem paths to read by tailing each file. A wild card (*) can be used in the paths; for example,/var/log/redis/*.log.
record_log_file_pathfalseIf set totrue, then the path to the specific file from which the log record was obtained appears in the output log entry as the value of theagent.googleapis.com/log_file_path label. When using a wildcard, only the path of the file from which the record was obtained is recorded.
typeThis value must beredis.
wildcard_refresh_interval60sThe interval at which wildcard file paths ininclude_paths are refreshed. Given as atime duration, for example30s or2m. This property might be useful under high logging throughputs where log files are rotated faster than the default interval.

What is logged

ThelogName is derived fromthe receiver IDs specified in the configuration. Detailed fields inside theLogEntryare as follows.

Theredis logs contain the following fields in theLogEntry:

FieldTypeDescription
jsonPayload.levelstringLog entry level
jsonPayload.messagestringLog message, including detailed stacktrace where provided
jsonPayload.pidnumberThe process ID issuing the log
jsonPayload.rolestringTranslated from redis role character (sentinel, RDB/AOF_writing_child, slave, master)
jsonPayload.roleCharstringRedis role character (X, C, S, M)
severitystring (LogSeverity)Log entry level (translated).

Configure metrics collection

To ingest metrics from Redis, you must create a receiver for the metricsthat Redis produces and then create a pipeline for the new receiver.

This receiver does notsupport the use of multiple instances in the configuration, for example, tomonitor multiple endpoints. All such instances write to the same time series,and Cloud Monitoring has no way to distinguish among them.

To configure a receiver for yourredis metrics, specify the followingfields:

FieldDefaultDescription
addresslocalhost:6379The URL exposed by Redis.
ca_filePath to the CA certificate. As a client, this verifies the server certificate. If empty, the receiver uses the system root CA.
cert_filePath to the TLS certificate to use for mTLS-required connections.
collection_interval60sAtime duration value, such as30s or5m.
insecuretrueSets whether or not to use a secure TLS connection. If set tofalse, then TLS is enabled.
insecure_skip_verifyfalseSets whether or not to skip verifying the certificate. Ifinsecure is set totrue, then theinsecure_skip_verify value is not used.
key_filePath to the TLS key to use for mTLS-required connections.
passwordThe password used to connect to the server.
typeThis value must beredis.

What is monitored

The following table provides the list of metrics that the Ops Agent collectsfrom the Redis instance.

Metric type 
Kind, Type
Monitored resources
Labels
workload.googleapis.com/redis.clients.blocked
GAUGEINT64
gce_instance
 
workload.googleapis.com/redis.clients.connected
GAUGEINT64
gce_instance
 
workload.googleapis.com/redis.clients.max_input_buffer
GAUGEINT64
gce_instance
 
workload.googleapis.com/redis.clients.max_output_buffer
GAUGEINT64
gce_instance
 
workload.googleapis.com/redis.commands.processed
CUMULATIVEINT64
gce_instance
 
workload.googleapis.com/redis.connections.received
CUMULATIVEINT64
gce_instance
 
workload.googleapis.com/redis.connections.rejected
CUMULATIVEINT64
gce_instance
 
workload.googleapis.com/redis.cpu.time
CUMULATIVEDOUBLE
gce_instance
state
workload.googleapis.com/redis.keys.evicted
CUMULATIVEINT64
gce_instance
 
workload.googleapis.com/redis.keys.expired
CUMULATIVEINT64
gce_instance
 
workload.googleapis.com/redis.keyspace.hits
CUMULATIVEINT64
gce_instance
 
workload.googleapis.com/redis.keyspace.misses
CUMULATIVEINT64
gce_instance
 
workload.googleapis.com/redis.latest_fork
GAUGEINT64
gce_instance
 
workload.googleapis.com/redis.memory.fragmentation_ratio
GAUGEDOUBLE
gce_instance
 
workload.googleapis.com/redis.memory.lua
GAUGEINT64
gce_instance
 
workload.googleapis.com/redis.memory.peak
GAUGEINT64
gce_instance
 
workload.googleapis.com/redis.memory.rss
GAUGEINT64
gce_instance
 
workload.googleapis.com/redis.memory.used
GAUGEINT64
gce_instance
 
workload.googleapis.com/redis.net.input
CUMULATIVEINT64
gce_instance
 
workload.googleapis.com/redis.net.output
CUMULATIVEINT64
gce_instance
 
workload.googleapis.com/redis.rdb.changes_since_last_save
GAUGEINT64
gce_instance
 
workload.googleapis.com/redis.replication.backlog_first_byte_offset
GAUGEINT64
gce_instance
 
workload.googleapis.com/redis.replication.offset
GAUGEINT64
gce_instance
 
workload.googleapis.com/redis.slaves.connected
GAUGEINT64
gce_instance
 

Verify the configuration

This section describes how to verify that you correctly configured theRedis receiver. It might take one or twominutes for the Ops Agent to begin collecting telemetry.

To verify that Redis logs are being sent toCloud Logging, do the following:

  1. In the Google Cloud console, go to theLogs Explorer page:

    Go toLogs Explorer

    If you use the search bar to find this page, then select the result whose subheading isLogging.

  2. Enter the following query in the editor, and then clickRun query:
    resource.type="gce_instance"log_id("redis")

To verify that Redis metrics are being sent toCloud Monitoring, do the following:

  1. In the Google Cloud console, go to the Metrics explorer page:

    Go toMetrics explorer

    If you use the search bar to find this page, then select the result whose subheading isMonitoring.

  2. In the toolbar of thequery-builder pane, select the button whose name is either MQL or PromQL.
  3. Verify thatPromQL is selectedin theLanguage toggle. The language toggle is in the same toolbar thatlets you format your query.
  4. Enter the following query in the editor, and then clickRun query:
    {"workload.googleapis.com/redis.clients.max_input_buffer", monitored_resource="gce_instance"}

View dashboard

To view your Redis metrics, you must have a chart or dashboardconfigured.The Redis integration includes one or more dashboards for you.Any dashboards are automatically installed after you configure theintegration and the Ops Agent has begun collecting metric data.

You can also view static previews of dashboards withoutinstalling the integration.

To view an installed dashboard, do the following:

  1. In the Google Cloud console, go to the Dashboards page:

    Go toDashboards

    If you use the search bar to find this page, then select the result whose subheading isMonitoring.

  2. Select theDashboard List tab, and then choose theIntegrations category.
  3. Click the name of the dashboard you want to view.

If you have configured an integration but the dashboard has not beeninstalled, then check that the Ops Agent is running. When there is nometric data for a chart in the dashboard, installation of the dashboard fails.After the Ops Agent begins collecting metrics, the dashboard is installedfor you.

To view a static preview of the dashboard, do the following:

  1. In the Google Cloud console, go to the Integrations page:

    Go toIntegrations

    If you use the search bar to find this page, then select the result whose subheading isMonitoring.

  2. Click theCompute Engine deployment-platform filter.
  3. Locate the entry for Redis and clickView Details.
  4. Select theDashboards tab to see a static preview. If the dashboard is installed, then you can navigate to it by clickingView dashboard.

For more information about dashboards in Cloud Monitoring, seeDashboards and charts.

For more information about using theIntegrations page, seeManage integrations.

Install alerting policies

Alerting policies instruct Cloud Monitoring to notify you whenspecified conditions occur.The Redis integration includes one or more alerting policies foryou to use.You can view and installthese alerting policies from theIntegrations page inMonitoring.

To view the descriptions of available alerting policies and install them, do the following:

  1. In the Google Cloud console, go to the Integrations page:

    Go toIntegrations

    If you use the search bar to find this page, then select the result whose subheading isMonitoring.

  2. Locate the entry for Redis and clickView Details.
  3. Select theAlerts tab. This tab provides descriptions of available alerting policies and provides an interface for installing them.
  4. Install alerting policies. Alerting policies need to know where to send notifications that the alert has been triggered, so they require information from you for installation. To install alerting policies, do the following:
    1. From the list of available alerting policies, select those that you want to install.
    2. In theConfigure notifications section, select one or more notification channels. You have the option to disable the use of notification channels, but if you do, then your alerting policies fire silently. You can check their status in Monitoring, but you receive no notifications.

      For more information about notification channels, seeManage notification channels.

    3. ClickCreate Policies.

For more information about alerting policies in Cloud Monitoring, seeIntroduction to alerting.

For more information about using theIntegrations page, seeManage integrations.

What's next

For a walkthrough on how to use Ansible to install the Ops Agent, configurea third-party application, and install a sample dashboard, see theInstall the Ops Agent to troubleshoot third-party applications video.

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-12-17 UTC.