DumbMonit

IntegraçõesBases de dados e mensagens

Monitorizar Redis / Valkey com o DumbMonit

The in-memory store itself: memory against maxmemory, refused connections, replication link and lag, failed saves and keyspace size.

DocumentaçãoSite oficial: Redis

As descrições estão em inglês, como no produto. Os rótulos da página seguem o seu idioma.

O que o DumbMonit vigia

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.

Utilização típica. In-memory store: memory against maxmemory, replication, persistence, keys

Exemplos

  • Redis
  • Valkey
  • The cache behind Nextcloud, Immich or Authentik

Como se liga

O que precisa

  • 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.

Não é preciso nenhuma conta.

Portas de rede a abrir

  • 6379/TCPRedis protocol (default port, plain or TLS)
Passos de configuração: Create a read-only Redis user
  1. In redis-cli, create the user (Redis 6 or later, or Valkey).

    ACL SETUSER dumbmonit on >a-long-password -@all +info +ping
  2. Save it: ACL SAVE if the server uses an aclfile, CONFIG REWRITE otherwise.

    ACL SAVE
  3. In DumbMonit, enter the server address, for example cache.lan:6380, then the user and its password.

  4. Tick TLS if the server only accepts TLS on that port (tls-port).

Atenção. On Redis 5 or older, or with only requirepass set, pick Password only: that password carries every right.