redis-observability

von redis

Redis-Observability-Anleitung – welche Metriken zu überwachen sind (Speicher, Verbindungen, Trefferquote, Operationen pro Sekunde, abgelehnte Verbindungen), welche integrierten Befehle verwendet werden sollten…

npx skills add https://github.com/redis/agent-skills --skill redis-observability

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.

MetricWhat it tells youAlert when
used_memoryCurrent memory usage> 80% of maxmemory
connected_clientsOpen connectionsSudden spikes or drops
blocked_clientsClients waiting on blocking ops> 0 sustained
instantaneous_ops_per_secCurrent throughputSignificant drops
keyspace_hits / keyspace_missesCache hit ratioHit ratio < 80%
rejected_connectionsHit maxclients cap> 0
rdb_last_save_timeLast persistence snapshotToo old vs. RPO
info = redis.info()
hit_ratio = info["keyspace_hits"] / max(1, info["keyspace_hits"] + info["keyspace_misses"])
print(f"Memory:    {info['used_memory_human']}")
print(f"Clients:   {info['connected_clients']}")
print(f"Ops/sec:   {info['instantaneous_ops_per_sec']}")
print(f"Hit ratio: {hit_ratio:.1%}")

See references/metrics.md.

2. Built-in commands for debugging

Reach for these when something looks off.

TopicCommand
Slow commandsSLOWLOG GET 10 / SLOWLOG LEN / SLOWLOG RESET
Server snapshotINFO all (or INFO memory / INFO stats / INFO clients / INFO replication)
Memory diagnosticsMEMORY DOCTOR / MEMORY STATS / MEMORY USAGE <key>
ConnectionsCLIENT LIST / CLIENT INFO
RQE / SearchFT.INFO <idx> / FT.PROFILE <idx> SEARCH QUERY "..."

The two most useful for incident triage:

  • SLOWLOG GET to find queries that exceeded the slowlog-log-slower-than threshold (10ms by default). The output shows the exact command and duration in microseconds.
  • MEMORY DOCTOR for memory pressure — it returns a one-paragraph summary of what's unusual about memory usage right now.
for entry in redis.slowlog_get(10):
    print(f"{entry['duration']}μs  {entry['command']}")

See references/commands.md.

3. Redis Insight

For interactive use (running queries, browsing keys, profiling indexes), Redis Insight is the official GUI. It surfaces the same SLOWLOG / INFO / FT.PROFILE data visually and includes Redis Copilot for natural-language queries. Useful during development and incident response; not a replacement for exporting metrics to your monitoring system.

References

Mehr Skills von redis

docs-sync
redis
Analysiere die Implementierung und Konfiguration des Master-Branches, um fehlende, falsche oder veraltete Dokumentation in docs/, README.md und paketspezifischen READMEs zu finden. Verwende…
official
implement-command
redis
Add a new Redis command (or command variant) to node-redis end-to-end — the `<NAME>.ts` Command file, its registration with JSDoc in the package…
official
maintainer-review
redis
Überprüfe eine GitHub-Issue- oder Pull-Request-URL als Node-Redis-Maintainer mit einer gestaffelten Bewertung, ob die Behauptung real, praktisch wichtig, bereits…
official
pr-draft-summary
redis
Erstelle den erforderlichen PR-fähigen Zusammenfassungsblock, Branch-Vorschlag, Titel und Entwurfsbeschreibung für node-redis. Muss vor der endgültigen Antwort verwendet werden, wann immer die…
official
runtime-behavior-probe
redis
Planen und Ausführen von Laufzeitverhaltensuntersuchungen mit temporären TypeScript-Probe-Skripten, Validierungsmatrizen, Zustandssteuerungen und ergebnisorientierten Berichten. Verwenden…
official
backend
redis
NestJS-Backend-Entwicklungsmuster für die RedisInsight-API: Modulstruktur, Services, Controller, DTOs, Dependency Injection und Fehlerbehandlung. Verwenden, wenn…
official
branches
redis
Kleinbuchstaben mit Bindestrichen verwenden, mit Typ-Präfix und Issue-/Ticket-Kennung. Branchnamen müssen den GitHub Actions Workflow-Regeln entsprechen (siehe .github/workflows/enforce-branch-name-rules.yml).
official
code-quality
redis
Code-quality standards for RedisInsight: TypeScript strictness, naming conventions (camelCase, PascalCase, UPPER_SNAKE_CASE), linting rules, no `any` without…
official