展示HN:BetterDB – 一款Valkey/Redis监控工具,能够持久化服务器遗忘的数据

1作者: kaliades大约 1 个月前原帖
嘿,HN,我是Kristiyan。我之前负责Redis Insight(官方Redis图形用户界面)。当我开始与Valkey合作时,发现可观察性工具不足,因此我开始构建BetterDB。 核心问题是:Valkey和Redis提供了有用的操作数据(慢日志、延迟统计、客户端列表、内存分解),但这些数据都是短暂的。重启服务器后,这些数据就消失了。现有工具可以显示实时图表,但无法告诉你在凌晨3点时,p99为何会激增。 BetterDB持久化这些短暂的数据,并将其转化为可操作的洞察: - 查询的历史分析(按类型聚合的慢日志和命令日志模式)、客户端(命令、连接、缓冲区)和ACL活动 - 异常检测和99个Prometheus指标 - 使用拓扑图和槽热图的集群可视化 - 自动化的延迟和内存诊断 - 用简单英语查询实例的AI助手(通过本地Ollama) - 性能开销低于1% 关于最后一点——我详细写了我们的交错A/B基准测试方法: [https://www.betterdb.com/blog/interleaved-testing](https://www.betterdb.com/blog/interleaved-testing)。大多数工具声称“最小开销”,却没有展示其依据。我们开源了基准测试套件,您可以在自己的硬件上运行并验证。 您现在可以尝试: ```bash npx @betterdb/monitor ``` 或者通过Docker: ```bash docker run -d -p 3001:3001 betterdb/monitor ``` BetterDB遵循开放核心模型,基于OCV开放章程(防止未来的许可变更)。社区版是免费的,具有真正的监控价值。专业版和企业版增加了历史持久性、警报和合规功能,但目前都是免费的,至少会持续到本月底。 我们在公开构建这个项目——基准测试套件、技术博客文章和路线图都已公开。希望能收到Valkey或Redis的生产用户对于可观察性缺口的反馈。 GitHub: [https://github.com/BetterDB-inc/monitor](https://github.com/BetterDB-inc/monitor) 博客: [https://www.betterdb.com/blog](https://www.betterdb.com/blog)
查看原文
Hey HN, I&#x27;m Kristiyan. I previously led Redis Insight (the official Redis GUI). When I started working with Valkey, I found the observability tooling lacking — so I started building BetterDB.<p>The core problem: Valkey and Redis expose useful operational data (slowlog, latency stats, client lists, memory breakdowns), but it&#x27;s all ephemeral. Restart your server and it&#x27;s gone. Existing tools show real-time charts but can&#x27;t tell you what happened at 3am when your p99 spiked.<p>BetterDB persists this ephemeral data and turns it into actionable insights:<p>- Historical analytics for queries (slowlog and commandlog patterns aggregated by type), clients (commands, connections, buffers), and ACL activity - Anomaly detection and 99 Prometheus metrics - Cluster visualization with topology graphs and slot heatmaps - Automated latency and memory diagnostics - AI assistant for querying your instance in plain English (via local Ollama) - Sub-1% performance overhead<p>On that last point — I wrote up our interleaved A&#x2F;B benchmarking methodology in detail: <a href="https:&#x2F;&#x2F;www.betterdb.com&#x2F;blog&#x2F;interleaved-testing" rel="nofollow">https:&#x2F;&#x2F;www.betterdb.com&#x2F;blog&#x2F;interleaved-testing</a>. Most tools claim &quot;minimal overhead&quot; without showing their work. We open-sourced the benchmark suite so you can run it on your own hardware and verify.<p>You can try it right now:<p><pre><code> npx @betterdb&#x2F;monitor </code></pre> Or via Docker:<p><pre><code> docker run -d -p 3001:3001 betterdb&#x2F;monitor </code></pre> BetterDB follows an open-core model under the OCV Open Charter (which prevents future licensing changes). The community edition is free with real monitoring value. Pro and Enterprise tiers add historical persistence, alerting, and compliance features, but are free for now and will be at least until end of month.<p>We&#x27;re building this in public — the benchmark suite, the technical blog posts, and the roadmap are all out in the open. Would love feedback from production users of Valkey or Redis on what observability gaps you&#x27;re still hitting.<p>GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;BetterDB-inc&#x2F;monitor" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;BetterDB-inc&#x2F;monitor</a> Blog: <a href="https:&#x2F;&#x2F;www.betterdb.com&#x2F;blog" rel="nofollow">https:&#x2F;&#x2F;www.betterdb.com&#x2F;blog</a>