This release adds 3 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
Summary
AI summaryKey Analytics screen adds largest‑keys ranking, keyspace size histogram, and one‑click deep scan.
Full changelog
Key Analytics: big-key detection & keyspace insights
A new Key Analytics screen surfaces where memory and hot traffic actually live in your Valkey/Redis keyspace - inspired by
valkey#1827.
New
- Largest Keys - top keys ranked by cardinality (element count for collections, byte length for strings), the true "big-key" signal, not just memory footprint. Each entry shows type, cardinality, memory, and TTL.
- Key Sizes - a server-side size histogram from
INFO keysizes(no keyspace scan). Available on Redis 8.0+; the tab degrades gracefully with an empty state on servers that don't expose the section. - Deep Scan - one-click full-keyspace scan for exact rankings, alongside the default sampled collection.
Details
- Per-key probing uses a single pipelined round-trip (
MEMORY USAGE,OBJECT IDLETIME/FREQ,TTL,TYPE, per-type length). - Sampled runs extrapolate pattern totals to full keyspace size; deep-scan visit counts are normalized to distinct-key totals to stay accurate under SCAN's duplicate visits.
- Working-set memory is bounded during deep scans by retaining only the top-N candidates per ranking signal.
- Collection refreshes the active tab immediately (no more tab-switch to see new data).
What's Changed
- feat(key-analytics): add largest-keys ranking, key-sizes histogram, deep scan by @KIvanow in https://github.com/BetterDB-inc/monitor/pull/288
Full Changelog: https://github.com/BetterDB-inc/monitor/compare/v0.24.0...v0.25.0
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About BetterDB-inc/monitor
Valkey-first observability with Redis compatibility. Query real-time metrics, analyze slow commands, detect hot keys, and investigate performance issues directly from AI coding assistants.
Related context
Related tools
Earlier breaking changes
- vagent-cache-py-v0.7.0 Cache keys changed for tool-using requests on the LlamaIndex adapter; existing cached entries will miss once after upgrade.
- vagent-cache-v0.7.0 Cache keys for tool-using requests changed on Vercel and LlamaIndex adapters; existing entries become one-time misses.
- vagent-v1.5.0 TLS is now mandatory; agent exits with error if `--valkey-tls true` is not set for IAM auth mode.
Beta — feedback welcome: [email protected]