Cache read breakdown
Each sample is a lookup against the in-memory keyspace: hit if the key existed with the expected Redis type (or any type for key probes). WRONGTYPE errors are not counted. Overall rate reflects how often work is satisfied inside MiniCache instead of implying a miss to your origin.
Where the numbers appear: the metric cards at the top of this page and the table below are drawn only after /api/minicache/summary returns OK. If they stay blank, check the status line in the header (errors often mean a missing dashboard key — open /dashboard?key=…).
Loading breakdown…
TCP / RESP capabilities
MiniCache speaks a Redis-shaped subset over TCP.
- Strings, hashes, lists, sets, sorted sets · TTL ·
SCAN/KEYS· transactions (MULTI/EXEC) - Pub/sub · blocking
BLPOP/BRPOP/BRPOPLPUSH· richerINFO(tryINFO server) - Optional shared password: set
RespServer:RequirePass— clients useAUTHbefore other commands
Commands
Cached keys
| Key | Type | Bytes | TTL (s) | Preview |
|---|
TCP clients
| Endpoint | Commands | Last command | Connected | Last activity |
|---|