Redis Observability

A practical reference for keeping Redis healthy in production. It lists the six metrics you should actually monitor (memory, connections, hit ratio, ops/sec, rejected connections, persistence lag) and the built-in commands that matter during an incident: SLOWLOG for finding slow queries, MEMORY DOCTOR for diagnosing pressure, CLIENT LIST for connection storms, and FT.PROFILE for search performance. The guidance is opinionated about alert thresholds (80% memory, sub-80% hit ratio) and includes minimal Python snippets for extracting what you need from INFO. Most useful when you're setting up monitoring for the first time or triaging a regression at 2am and need to remember which Redis command actually helps.

skills.sh installs: 2.5K
GitHub stars: 175
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add redis/agent-skills --skill redis-observability --agent claude-code

Installs into .claude/skills of the current project.

Files

Redis Observability

What to watch, what to run, and what to alert on. Covers the metrics every Redis deployment should monitor and the built-in commands for ad-hoc diagnosis.

When to apply

Setting up monitoring or alerts for a Redis instance.
Diagnosing a Redis performance regression (high latency, memory pressure, connection storms).
Profiling a slow FT.SEARCH or pipeline.
Wiring Redis metrics into Prometheus, Datadog, CloudWatch, or similar.

1. Monitor these metrics

These come from INFO and should be exported to your monitoring system.

Metric	What it tells you	Alert when
`used_memory`	Current memory usage	> 80% of `maxmemory`
`connected_clients`	Open connections	Sudden spikes or drops
`blocked_clients`	Clients waiting on blocking ops	> 0 sustained
`instantaneous_ops_per_sec`	Current throughput	Significant drops
`keyspace_hits` / `keyspace_misses`	Cache hit ratio	Hit ratio < 80%
`rejected_connections`	Hit `maxclients` cap	> 0
`rdb_last_save_time`	Last persistence snapshot	Too old vs. RPO