IntégrationsBases de données et messagerie
Surveiller Redis / Valkey avec DumbMonit
The in-memory store itself: memory against maxmemory, refused connections, replication link and lag, failed saves and keyspace size.
DocumentationSite officiel : Redis
Les descriptions des produits sont en anglais, comme dans le produit. Les libellés de la page suivent votre langue.
Ce que DumbMonit surveille
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.
Usage typique. In-memory store: memory against maxmemory, replication, persistence, keys
Exemples
- Redis
- Valkey
- The cache behind Nextcloud, Immich or Authentik
Comment il se connecte
Ce qu'il faut
- 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.
Aucun compte nécessaire.
Ports réseau à ouvrir
6379/TCPRedis protocol (default port, plain or TLS)
Étapes de mise en place: 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).
À savoir. On Redis 5 or older, or with only requirepass set, pick Password only: that password carries every right.