Diagnose Redis failures using Netdata MCP signals and a triage tree.
npx skills add https://github.com/netdata/skills --skill troubleshoot-redis
Please help me install this Agent Skill. Skill: troubleshoot-redis Source: https://github.com/netdata/skills/tree/main/skills/troubleshoot-redis Command: npx skills add https://github.com/netdata/skills --skill troubleshoot-redis
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.
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."
High-intent search queries and answers about installing and using this skill.
Diagnose Redis outage patterns by routing an AI through a structured triage tree mapped to failure domains like fork/cow storms, event loop wedges, and memory pressure spirals. It queries Netdata signals for reachability, uptime, memory fragmentation, and rejected connections to validate the suspected archetype.
Redis memory pressure spirals and connection exhaustion cascades occur when memory fragmentation ratios and rejected connections exceed expected thresholds. A structured diagnostic tree queries Netdata for these specific metrics, verifying the failure archetype and guiding targeted remediation.
Troubleshoot Redis replication backlog overflow by querying Netdata for replication health metrics. The diagnostic tree targets replication as a specific failure domain, validating the overflow archetype against live signals before recommending remediation steps.
Yes, Netdata MCP signals drive structured root-cause analysis for Redis incidents. The operator-playbook triage tree queries reachability, memory usage, and replication health to confirm failure archetypes and validate post-remediation signal normalization.
Verify Redis remediation by re-running the same Netdata MCP signal queries after applying fixes. The remediation-focused confirmation loop checks whether metrics like event loop responsiveness and uptime return to expected ranges rather than stopping at the first anomaly.
Yes, this Redis troubleshooting approach targets on-call triage specifically. It maps a structured diagnostic path across liveness, memory, connections, throughput, persistence, and replication domains to quickly identify common failure archetypes during active incidents.
netdataDiagnose PostgreSQL incidents using Netdata MCP queries and structured triage.
netdataDiagnose Docker Engine incidents via Netdata MCP queries and operator playbook triage.
netdataTroubleshoots Apache ActiveMQ Classic 5.x failures using Netdata MCP-based diagnostic triage.
redisGuide Redis monitoring with INFO metrics, diagnostic commands, and Redis Insight.
