Shipped · Observability

What BetterDB-inc/monitor shipped

The public repository of Betterdb · github.com/BetterDB-inc/monitor

Written by FoxPlug from the repository's own releases; not affiliated with Betterdb. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/BetterDB-inc/monitor; Betterdb did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for monitor, free

Week of November 2, 2026

What shipped

Why it matters

This week moves anomaly detection onto per-node and per-replica signals, so a single registered seed connection can still surface divergence, retry amplification and reshard skew across a cluster. It also fixes self-inflicted alert noise from key analytics and duplicate stall webhooks. The v0.54.0 release brings mutual TLS and the new failure patterns to anyone running BetterDB against production Redis.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V0.54.0 is out: mutual TLS with client certificates and private CA verification. Anomaly detection now reaches every cluster shard and Sentinel group, divergence is checked against each replica's own offset, and incident timelines have a dashboard tab.

Post for LinkedIn

BetterDB v0.54.0 is out. Mutual TLS support lets BetterDB present a client certificate, verify a private CA and authenticate by certificate alone with no AUTH. Replication divergence now runs on every cluster shard and Sentinel group rather than only registered primaries, retry amplification is evaluated per node, and each replica's byte gap is cross-checked against its own offset. The anomaly dashboard has a new Incidents tab for timelines, and Prometheus now gets gauges alongside the existing event counters. Key analytics no longer trigger error and retry alerts from its own commands, and a single webhook is sent per replica stall when both nodes are monitored.

Week of October 12, 2026

What shipped

Why it matters

This week key analytics stopped assuming everything lives in db0, so instances that keep keys in other logical databases are now visible in the UI, API, metrics and dashboards. Writes that the server is actively refusing now produce their own events, covering an outage type that memory, CPU and latency signals did not catch. Key-size metrics also reach Prometheus and OTLP, so growth can be alerted on before it turns into a memory problem.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Key analytics now scans every non-empty logical database, not just db0. Write rejections like OOM and READONLY now raise their own events. Key-size gauges export to Prometheus and OTLP. Plus stream consumer groups survive command-mode migrations.

Post for LinkedIn

This week's changes focus on seeing what was previously invisible. Key analytics now scans every non-empty logical database and honors the configured dbIndex, carrying the database through the UI, API, Prometheus metrics and dashboards; previously a scan could report no keys while thousands sat in another database. Write rejections including MISCONF, OOM, READONLY and NOREPLICAS now raise writes.rejected and writes.recovered events, covering outages that memory, CPU and latency signals miss. Key-size gauges join the Prometheus and OTLP exports so ballooning keys can be alerted on early. Stream consumer groups are kept during command-mode migrations, and threshold alert state is now scoped per connection.

Week of September 28, 2026

What shipped

Why it matters

This release removes two manual setup bottlenecks: you no longer register cluster and Sentinel nodes by hand, and you can monitor instances that push metrics to BetterDB instead of BetterDB pulling from them. Both features are opt-in, making the monitoring setup process significantly faster for Redis/Valkey deployments at scale.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V0.48.0: cluster and Sentinel nodes auto-register themselves, and external instances can push OTLP metrics instead of waiting for BetterDB to pull. Everything stays opt-in.

Post for LinkedIn

V0.48.0 ships two major improvements to deployment workflows: automatic cluster node discovery from a single seed connection, Sentinel failover tracking, and the ability to ingest metrics from instances pushing OTLP data. No more manual node registration, no requirement for direct connectivity. Both features opt-in.

Week of September 14, 2026

What shipped

Why it matters

Self-hosted deployments now have full user authentication and access control, matching cloud features. The agent can run on self-hosted with workspace auth. Webhook integrations work better with platform-specific formatting for Slack and Discord.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V0.44.0: self-hosted installs get authentication, agent support, personal tokens, and Google/GitHub sign-in. Agent 1.6.2 fixes npm/Docker crashes. Webhooks format for Slack and Discord.

Post for LinkedIn

V0.44.0 brings user control to self-hosted BetterDB: sign-in with Google/GitHub, personal tokens, activity logs, and invitations. Agent feature now works on self-hosted with workspace auth. Agent 1.6.2 fixes build issues in npm and Docker. Webhooks support Slack and Discord payload formats. Fleet overview helps cloud teams monitor multi-instance health.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-11.

Is this your repo? Ask us to remove this page.