managing-redis-deep

name	managing-redis-deep
description	Use when working with Redis Deep — advanced Redis management including cluster topology, sentinel failover, streams analysis, Lua script auditing, module inspection, and memory defragmentation. Covers RDB/AOF persistence tuning, pub/sub diagnostics, client-side caching, and ACL configuration. Read this skill before any advanced Redis operations.
connection_type	redis
preload	false

Redis Deep Management Skill

Advanced Redis cluster, streams, and module management beyond basic key/value operations.

MANDATORY: Discovery-First Pattern

Always run INFO ALL and check cluster/sentinel mode before any advanced operations. Never assume topology or module availability.

Phase 1: Discovery

#!/bin/bash

redis_cmd() {
    redis-cli -h "$REDIS_HOST" -p "${REDIS_PORT:-6379}" \
              ${REDIS_PASSWORD:+-a "$REDIS_PASSWORD"} \
              --no-auth-warning "$@"
}

echo "=== Server & Mode ==="
redis_cmd INFO server | grep -E 'redis_version|redis_mode|os|uptime_in_days|executable|config_file'

echo ""
echo "=== Cluster Detection ==="
redis_cmd CLUSTER INFO 2>/dev/null | head -5 || echo "Cluster mode: disabled"

echo ""
echo "=== Sentinel Detection ==="
redis_cmd INFO sentinel 2>/dev/null | head -10 || echo "Sentinel: not running"

echo ""
echo "=== Loaded Modules ==="
redis_cmd MODULE LIST 2>/dev/null || echo "No modules loaded (or Redis < 4.0)"

echo ""
echo "=== ACL Users ==="
redis_cmd ACL LIST 2>/dev/null | head -10 || echo "ACL not available (Redis < 6.0)"

echo ""
echo "=== Streams Overview ==="
redis_cmd SCAN 0 TYPE stream COUNT 100 2>/dev/null | tail -n +2 | while read key; do
    len=$(redis_cmd XLEN "$key" 2>/dev/null)
    groups=$(redis_cmd XINFO GROUPS "$key" 2>/dev/null | grep -c "name" || echo "0")
    echo "Stream: $key | Length: $len | Groups: $groups"
done

Phase 1 outputs: Redis version/mode, cluster/sentinel state, loaded modules, ACL users, stream inventory.

Phase 2: Analysis

#!/bin/bash

redis_cmd() {
    redis-cli -h "$REDIS_HOST" -p "${REDIS_PORT:-6379}" \
              ${REDIS_PASSWORD:+-a "$REDIS_PASSWORD"} \
              --no-auth-warning "$@"
}

echo "=== Memory Defragmentation ==="
redis_cmd INFO memory | grep -E 'mem_fragmentation|active_defrag|allocator_frag'

echo ""
echo "=== Persistence Health ==="
redis_cmd INFO persistence | grep -E 'rdb_|aof_|loading'

echo ""
echo "=== Pub/Sub Channels ==="
redis_cmd PUBSUB CHANNELS '*' 2>/dev/null | head -10
redis_cmd PUBSUB NUMSUB 2>/dev/null | head -10

echo ""
echo "=== Client List Summary ==="
redis_cmd CLIENT LIST | awk -F'[ =]' '{
    for(i=1;i<=NF;i++) {
        if($i=="cmd") cmd=$(i+1)
        if($i=="flags") flags=$(i+1)
    }
    print cmd, flags
}' | sort | uniq -c | sort -rn | head -10

echo ""
echo "=== Latency History ==="
redis_cmd LATENCY LATEST 2>/dev/null || echo "Latency monitoring not enabled"

echo ""
echo "=== Cluster Slot Coverage ==="
redis_cmd CLUSTER SLOTS 2>/dev/null | head -20 ||  

Output Format

REDIS DEEP ANALYSIS
====================
Version: [version] | Mode: [standalone/cluster/sentinel]
Modules: [list] | Streams: [count]

ISSUES FOUND:
- [issue with affected component]

RECOMMENDATIONS:
- [actionable recommendation]

Anti-Hallucination Rules

1. NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
2. NEVER fabricate metric names or dimensions — verify against the service documentation or --help output.
3. NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
4. ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
5. ALWAYS handle empty results gracefully — an empty response is valid data, not an error to retry.

Counter-Rationalizations

Shortcut	Counter	Why
"I'll skip discovery and check known resources"	Always run Phase 1 discovery first	Resource names change, new resources appear — assumed names cause errors
"The user only asked for a quick check"	Follow the full discovery → analysis flow	Quick checks miss critical issues; structured analysis catches silent failures
"Default configuration is probably fine"	Audit configuration explicitly	Defaults often leave logging, security, and optimization features disabled
"Metrics aren't needed for this"	Always check relevant metrics when available	API/CLI responses show current state; metrics reveal trends and intermittent issues
"I don't have access to that"	Try the command and report the actual error	Assumed permission failures prevent useful investigation; actual errors are informative