Database / BetterDB Interview questions
Why is COMMANDLOG exclusive to Valkey rather than Redis in BetterDB Monitor?
COMMANDLOG is a server-side feature that Valkey introduced starting at 8.1 – it isn't a command that exists in any released version of Redis, so there's simply nothing for BetterDB to call, even with its Redis 6+ compatibility mode.
SLOWLOG, which both databases support, is the closest Redis equivalent, but it only tracks a duration threshold, not the large-request/large-reply cases COMMANDLOG is designed for.
Because BetterDB's adapter detects the connected server's type and version up front, it simply hides the COMMANDLOG-dependent panels when talking to Redis, or to Valkey older than 8.1, rather than trying to fake the data or throwing an error.
This is a good example of how BetterDB treats Redis 6+ compatibility: it's not pretending every feature works identically everywhere, it's using per-version capability detection so the feature set you see is always an honest reflection of what the connected server can actually provide.
More Related questions...
