• /
  • EnglishEspañolFrançais日本語한국어Português
  • EntrarComeçar agora

Redis (OpenTelemetry) metrics reference

This reference guide provides a comprehensive overview of all metrics collected by the Redis OpenTelemetry integration, helping you understand what data is available for monitoring your Redis instance health and performance.

Key metrics at a glance

Monitor your Redis instance health and performance with these essential metrics:

Metric category

What it measures

Priority

Memory utilization

redis.memory.used, redis.maxmemory — Current memory consumption vs configured limit

Critical

Cache hit ratio

redis.keyspace.hits, redis.keyspace.misses — Ratio of successful key lookups

Critical

Key evictions

redis.keys.evicted — Keys removed due to memory pressure

Critical

Commands/sec

redis.commands, redis.commands.processed — Throughput of commands being executed

Important

Connected clients

redis.clients.connected, redis.clients.blocked — Active and waiting connections

Important

Fragmentation ratio

redis.memory.fragmentation_ratio — Ratio of OS-allocated to Redis-allocated memory

Monitoring

Cluster health

redis.cluster.state, redis.cluster.slots_ok, redis.cluster.known_nodes — Overall cluster status and slot coverage (Cluster mode only)

Critical

Complete metrics reference

The integration collects 30+ instance metrics across commands, memory, keyspace, connections, and replication — plus 9 cluster-specific metrics for Redis Cluster deployments. Expand the sections below for detailed metric specifications.

Cluster metrics

These metrics are only available when monitoring Redis in Cluster mode. They require enabling cluster metrics in the Redis receiver (all cluster metrics are disabled by default) or using the Prometheus receiver approach with redis_exporter --is-cluster.

Metric

Description

Type

redis.cluster.state

Overall cluster health status. 1 = OK (all slots served), 0 = FAIL (one or more slots unavailable).

Gauge

redis.cluster.slots_assigned

Number of hash slots mapped to nodes. Must be 16384 for a fully operational cluster.

Gauge

redis.cluster.slots_ok

Number of slots actively serving requests without issues.

Gauge

redis.cluster.slots_pfail

Number of slots in PFAIL (probable failure) state — a node is suspected unreachable but not yet confirmed.

Gauge

redis.cluster.slots_fail

Number of slots in confirmed FAIL state — NOT serving traffic.

Gauge

redis.cluster.known_nodes

Total number of nodes (masters + replicas) visible in the cluster.

Gauge

redis.cluster.node.count

Number of master nodes currently serving hash slots.

Gauge

redis.cluster.stats_messages_sent

Total cluster bus messages sent (ping, pong, meet, fail). Steady traffic indicates healthy gossip protocol.

Cumulative

redis.cluster.stats_messages_received

Total cluster bus messages received from peer nodes. A sudden drop indicates possible network partition.

Cumulative

Dica

All nodes in a Redis Cluster report identical cluster metrics (CLUSTER INFO returns the same data from any node). You can enable cluster monitoring on all nodes for resilience or on a single node to minimize redundant data. For the Prometheus receiver approach, use redis_exporter --is-cluster which automatically collects these metrics.

Resource attributes

Resource attributes are attached to all metrics and help you filter and group your data in New Relic.

Attribute

Description

server.address

Hostname or IP of the Redis server

server.port

Port number of the Redis server

redis.instance.id

Custom identifier for the Redis instance

redis.version

Redis server version

host.name

Hostname where the collector is running

host.id

Unique identifier of the host

k8s.cluster.name

Kubernetes cluster name

k8s.namespace.name

Kubernetes namespace

k8s.pod.name

Kubernetes pod name

redis.cluster.name

User-defined Redis Cluster name (only present on cluster metrics)

instrumentation.provider

Always opentelemetry

otel.library.name

Instrumentation library name

Next steps:

Copyright © 2026 New Relic Inc.

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