Ask Redis

Attach a server and ask. Verbiqo reads the server’s own counters and logs, never your keys or values.

Attach

/redis cache

Verbiqo shows the product, version and role, with the number of clients and keys.

What to ask

You want to know	Ask, for example	What Verbiqo does first
What is wrong now	Redis is slow right now, why?	Samples the counters for 10 seconds: commands a second, how busy the main thread is, evictions, refused connections. Then the slow log, latency events and clients with large buffers.
Memory	Why is Redis using so much memory?	Use against maxmemory and the eviction policy, fragmentation, swap.
Persistence	Are snapshots working?	The last snapshot and AOF write, and whether a restart would lose data.
Replication and cluster	Is the replica in sync? Is the cluster healthy?	Each replica’s link and lag, full resyncs, cluster state, failed nodes, primaries without a replica.
Clients	Who is connected?	Clients against maxclients, idle connections by host, refused connections.
Security	Is this Redis secure?	Tries a connection without a password (PING only), checks binding, TLS and dangerous commands.
What happened	What happened in the last hour?	A timeline of the restart, the last snapshot, a lost primary, latency events and the slowest commands, with the Redis log and the machine when attached.
Capacity	When will Redis hit maxmemory?	Memory, clients, CPU and disk forecasts (Capacity planning).
What Verbiqo can see	What should I enable?	Each item in Settings that help, as ready or not.

Every check and the words that bring it in: Redis checks.

What happened earlier

/splunk prod
/redis cache
/prom prod

Splunk adds the Redis and Sentinel logs (Log findings); Prometheus adds redis_exporter’s memory and client history and the machine’s.

From a terminal

In verbiqo chat, attach with /redis as in the app. To run one report, or one command from the read list:

verbiqo redis run cache slowlog
verbiqo redis command cache "INFO memory"

Reports for run: overview, memory, memory-doctor, stats, clients, connections, slowlog, latency, latency-doctor, replication, persistence, keyspace, commandstats, errorstats, cluster, settings.