troubleshoot-redis

What problem does it solve?

Redis incidents often follow recurring failure archetypes like replication backlog overflow, memory pressure spirals, or event loop wedges that are hard to diagnose from generic “is it up?” checks.

Core Features & Use Cases

• Operator-playbook triage tree: Routes an AI through a structured diagnostic path mapped to Redis failure domains (liveness/state, memory, connections, throughput/latency, persistence, replication).
• Netdata MCP-driven verification: Queries Netdata via MCP for Redis reachability, uptime/restarts, memory usage and fragmentation, rejected connections, and replication health to validate the suspected archetype.
• Remediation-focused confirmation loop: Re-runs the same signal queries after suggested fixes to confirm signals return to expected ranges rather than stopping at the first anomaly.

Quick Start

Ask the agent: "Diagnose my Redis outage pattern using Netdata MCP metrics and recommend a remediation based on the fork/cow storm, event loop wedge, replication backlog overflow, memory pressure spiral, or connection exhaustion cascade."