Redis Plugin

The Redis plugin registers standalone, primary/replica, and Redis Cluster deployments as one Konduo resource and exposes status, metrics, diagnostics, and bounded management workflows.

Highlights

• Discovers cluster node IDs and member addresses from the seed endpoint and represents them as target evidence within one resource instance.
• Provides logical metrics for memory, keyspace, command throughput, clients, evictions, fragmentation, replication, and blocked clients.
• Supports both Prometheus mapping packs and Konduo-managed Redis metric collection.
• Runs key scan, streams, CLI, memory inspection, and server operations through bounded jobs and confirmation boundaries.

Before Registration

• Prepare seed host/port and password or ACL user credentials.
• For clustered deployments, cluster_instances can provide a fallback member list.
• Prepare Prometheus redis_exporter mapping or a managed collection write target for metric-backed views.
• When Prometheus is the managed collection write target, run Prometheus with --web.enable-remote-write-receiver.

Operations Tips

• Do not treat seed endpoint failure as whole-cluster failure without checking other discovered members.
• Interpret memory fragmentation, evictions, and blocked clients together with workload changes.
• Key and stream scans can add load; review limits, cursor behavior, and job status before running them.
• Bulk-key, import, and big-key job results are temporary in-memory evidence, not audit history. Completed results disappear automatically after their bounded viewing window and all such results are lost when the plugin restarts.
• Deep-diagnostics results, CLI execution streams/history, and server-operation status are also bounded process-local evidence. CLI snippets and favorites are user configuration and are not removed by execution-result cleanup.

Operator Views

• The server view shows standalone, primary/replica, and cluster members inside one resource instance while distinguishing the seed endpoint from discovered members.
• The key view uses cursor-based scan jobs to inspect bounded key lists, TTL, type, and estimated memory.
• The Streams view exposes stream, group, consumer, pending backlog, and idle-time evidence as read-only operational data.
• CLI and server-operation views run only selected triage commands behind confirmation and safe-mode controls.

Diagnostics And Alerts

• Diagnostics are grouped by topology, memory/keyspace posture, workload attribution, durability/replication, and metric-backed risk.
• Alert rules cover cluster health, replication link state, replication lag, fragmentation, blocked clients, evictions, and cache hit-rate risk.
• Managed collection converts Redis command evidence into redis_exporter-compatible samples and isolates them with the resource identity label.
• Missing metric evidence should lead operators to inspect mapping packs, scrape state, or managed-write status instead of assuming Redis is healthy.

Management Boundary

• Arbitrary Redis API browsing and unbounded KEYS scans are outside the CE operating boundary.
• Key deletion, server operations, and CLI execution are mutating actions that require intent confirmation, permissions, and audit evidence.
• Mutating stream workflows such as trim, claim, or ack are not provided without separate guardrails.
• When seed endpoints or cluster member identities change, refresh both resource configuration and cluster evidence to avoid stale discovery.

Example Workflows

• For memory alerts, compare used/max memory, fragmentation, eviction rate, keyspace growth, and big-key scan results.
• For replication lag, review primary/replica role, link state, replication offsets, and network evidence together.
• For cluster-slot issues, inspect member reachability, cluster-nodes evidence, slot completeness, and failover progress.
• For stream delay, check pending count, consumer idle time, last-delivered id, and retention policy in order.

---

Redis Enterprise Overlay

The Redis Enterprise overlay adds MCP descriptors, Enterprise dashboards, diagnostic analysis jobs, key scans, bulk jobs, import/export, streams, CLI console, and anomaly detectors to the Community Redis plugin.

Highlights

• Exposes monitoring overview, topology summary, diagnostics, metrics catalog, and alert/anomaly rules through MCP.
• Plugin-executed anomaly detectors interpret INFO evidence for memory pressure, blocked clients, and replication link down.
• Big key scans, stream inspection, bulk TTL/delete, import/export, and CLI execution run as bounded jobs.
• Log evidence blueprints connect OOM, failover, connection refused, and slowlog patterns to an Enterprise log source.

Before Registration

• Community Redis connectivity, ACLs, cluster discovery, and metric-source mapping must be healthy.
• Review operator permissions and audit requirements before enabling key scan or CLI workflows.
• Connect an OpenSearch log source when richer diagnostic evidence is needed.

Operations Tips

• Do not treat seed endpoint failure as whole-cluster failure without checking other discovered members.
• Interpret memory fragmentation, evictions, and blocked clients together with workload changes.
• Key and stream scans can add load; review limits, cursor behavior, and job status before running them.
• Import/export and bulk jobs can add load in large estates. Review limits, dry-run mode, and job status.
• Bulk-key, import, and big-key job results are temporary in-memory evidence, not audit history. Completed results disappear automatically after their bounded viewing window and all such results are lost when the plugin restarts.
• Deep-diagnostics results, CLI execution streams/history, and server-operation status are also bounded process-local evidence. CLI snippets and favorites are user configuration and are not removed by execution-result cleanup.
• Use MCP descriptors as read-oriented context; mutating jobs must keep existing action routes and authorization boundaries.

Operational Scenarios

• For suspected memory pressure, review INFO evidence, big-key scans, eviction, fragmentation, and slowlog or log evidence together.
• For stream backlog or consumer-group issues, use stream inspection and topology summaries to narrow the delayed processing point.
• Run import/export or bulk TTL/delete only after checking operator intent, dry-run output, job progress, and audit trail.

Boundaries

• CLI console, bulk jobs, and import/export are powerful operational features and must stay behind action routes separate from MCP read-only descriptors.
• Redis plugin-mode anomaly detection focuses on INFO evidence; log correlation is connected through OpenSearch log source mappings.