DumbMonit
IntegrationsDatabases and messaging
Monitor Redis / Valkey with DumbMonit
The in-memory store itself: memory against maxmemory, refused connections, replication link and lag, failed saves and keyspace size.
DocumentationOfficial website: Redis
Product descriptions are in English, as in the product. The page labels follow your language.
What DumbMonit watches
The in-memory store itself: memory against maxmemory, refused connections, the replication link and the lag of each replica, failed snapshots and append-only file writes, and the size of the keyspace.
Typical use. In-memory store: memory against maxmemory, replication, persistence, keys
Examples
- Redis
- Valkey
- The cache behind Nextcloud, Immich or Authentik
How it connects
What you need
- ACL user (recommended)A Redis user allowed to run INFO and PING only. Sent as AUTH user password.
- Password onlyFor Redis 5 or older, or a server with only requirepass set. Sent as AUTH password.
No account needed.
Network ports to open
6379/TCPRedis protocol (default port, plain or TLS)
Setup steps: Create a read-only Redis user
In redis-cli, create the user (Redis 6 or later, or Valkey).
ACL SETUSER dumbmonit on >a-long-password -@all +info +pingSave it: ACL SAVE if the server uses an aclfile, CONFIG REWRITE otherwise.
ACL SAVEIn DumbMonit, enter the server address, for example cache.lan:6380, then the user and its password.
Tick TLS if the server only accepts TLS on that port (tls-port).
Heads-up. On Redis 5 or older, or with only requirepass set, pick Password only: that password carries every right.